|CS425 - Systems Analysis and Design|
Update: August 31, 2006
H: (970)229-9282 C: (970)690-9976
5% lost for every week a homework is late (unless other arrangements are made), no homework can be turned in past last night of class.
This class is an overview of how to Develop a Systems Design for a Software Project. This process includes all of the planning and analysis needed to complete a good design. It does not include the actual implementation of the project. However, at the end of the class you should have a good design for the project and scheduling for the implementation and release phases of the project. Because most software projects are done using Object Oriented techniques, there will be some overlap between this course and the CS432 - Object Oriented Analysis & Design class. If you are planning to take the CS445 - Database Management class after this class, I would suggest designing a project that uses a Database, so that you can already have your design ready when you start your DBMS class and can then implement your project in the DBMS class.
Please note that the readings in this assignment are based on the sixth edition of the textbook. The textbook has been upgraded to the seventh edition, so updates to this document are needed. Please proceed with the topics as outlined here. The chapters may have changed with the new edition of the textbook. You may wish to review the full class syllabus as presented by Regis for a better understanding.
Since I do teach CS432, I am starting to put together a set of web pages that describes the similarities and differences between Systems and Object Oriented Analysis and Design. Please reference this site for an overview and the Q and A that cover this class and CS432.
Please review the needed materials as listed in the First Class Module description. This web site will give you the first nights assignment and the needed reading. Please note that in order to access this location, you need a Regis login and password.
Week 1 Whitten/Bentley/Dittman – Systems Analysis & Design Methods: Chapters 1 - 3
H/W – Choose general topic, fill out “Problem Statement Matrix” document from book this for this general topic and four to five additional subtopics.
Week 2 W/B/D: Chapters 4 – 6:
C/W – Discuss topics from your “Problem Solving Matrix” and pick one topic to develop with one or perhaps two other people. Remember this design must be completed by the end of this eight week course.
H/W Based on your “Problem Statement Matrix” and the Problem selected, you need to fill out the Introduction and Scope for your project (based on "Study Report - for Problem Analysis Phase" template on book disk). Create Initial System Development Schedule (Gantt and Pert Chart from Microsoft Project, or similar software) assuming Decision Analysis ends and Physical Design begins on the last night of the class. Also create an Ishiwaka Diagram and an Expectation Management Matrix (book disk) for your project (10 points each)..
Week 3 W/B/D Chapters 7 -8
H/W Update your schedule and your Ishiwaka Diagram for your project and create an Entity Relationship Diagram (remember discussions on pages 304-305 that state that there should be no “many to many” relationships and that the attributes will be added next week). (20 points). Prepare a Project Status Report (1/2 to ¾ page)
Week 4 W/B/D Chapters 9-11
H/W You need to create Use Cases, add the major attributes to your Entity Relationship Diagram, and create a Data Flow Diagram for your project. (20 points)
Midterm Quiz – Traded Quiz/Test for Chapter 12-18 Student Presentations.
Based on Key Terms covered in margins of W/B/D chapters 1-8
Week 5 W/B/D Chapters 12 -14 and alternate scheduling tool (see assignments on the next page).
H/W Delivery based on your schedule (this should include a Cost Analysis Report, along with Project Status Report (20 points)
Week 6 W/B/D Chapters 15 -18 (see assignments on the next page).
H/W Delivery based on your schedule, along with Project Status Report (20 points)
Week 7 Final Exam – Do Chapter 12-18 Presentations instead
A review of your project progress will be .made at this point. Your projects should be nearing completion. Any additional items that need to be discussed will be at this time.
C/W – Each team will run a milestone meeting for another team. The milestone meeting is based on the Joint Requirements Planning (JRP) Meeting as discussed on pages 257-262. (20 points)
Week 8 Class Presentations (30 points)
Papers (40 points)
Teamwork based on other member feedback (20 points)
Class Presentations and Papers should include procedures learned in this class and some example of tools described in this class (i.e. Microsoft Visio and/or Project). It must include examples of the final versions of the documents created as homework in this class.
Week 5-6 Presentations:
This site was last updated 09/02/06