SYST 510 - Systems Definition and Cost Modeling

Spring 2004



Dr. Peggy Brouse


WebCT Instructions

Work Phone:

(703) 993-1502 (with voice mail)


(703) 993-1706



GMU:  Science and Technology II - Room 317

Office Hours:

Mondays  11:30 - 1: 00 and by appointment

Course Description:

During this course, the Systems Definition phase of the Systems Development Life Cycle will be explored.  This phase of the systems engineering effort includes such activities as requirement elicitation, problem analysis, system specification, and system cost estimation.  Lectures concerning these topics will be given by the instructor and will be supported by the listed texts.  Students will be tested to ensure understanding of material contained within the lectures and the texts.  Additionally, students will gain practical knowledge concerning this subject by participating in a group project to create a System Requirement Specification (SRS) and cost model of the system to be developed. 

Course Hours:

Wednesday  4:30 p.m. to 7:10 p.m.; Room 131 Innovation and JD Learning Center, Dahlgreen, Virginia


Requirements Engineering Processes & Techniques (1998) Ian Sommerville and Gerald Kotonya. John Wiley and Sons ISBN 0-471-97208-8


50% - group project: (5% SOW; 20% Final Presentation; 25% Final Deliverable)


25% - midterm


25% - final

Group Project

The Group Project is the focal point of student effort within this course.  Although groups may be able to meet during class time occasionally, the majority of effort toward the group projects will be expended outside of class.  There will be groups of several people self-formed during the first meeting of the class.  Each group will have two roles: User Group and Requirement Group. 

Beginning User Group Activities:  As a user, the group will formulate a Statement of Work (SOW) that they will pass to their “mate group”.  Mate groups will be assigned after the SOW is completed. 

Beginning Requirement Group Activities:  Each group will exchange their SOW with their assigned mate group.  The SOW that they receive from their mate group will form the basis for their role as a Requirement Group.  In this role, they will

·        study the SOW they have received,

·        elicit requirements from the mate group to develop a Systems Requirement Specification (SRS) including problem analysis and system definition models,

·        run cost models and document their final SRS. 

Each member of the group will be required to run a different cost model (e.g. COCOMO2, SoftEst, etc.).  This individual run of the model will constitute the second test for the course.  The final analysis of the cost models will be a comparison of the individual models with a determination by the group of the final estimation they submit.  Their mate group will be doing these same functions with the SOW they receive. 

Ending User Group Activities:  After completion of the SRS and cost models, the mate groups will again exchange documents: the SRS and Cost Model document.  In the User Group role, each group will evaluate the products of their mate group.  A recommended evaluation strategy will be given to you.

Ending Requirement Group Activities:  At the end of the semester, each group will present their work including the SRS and Cost Models.  Groups will be required to hand in their final package to the professor including:

·        original annotated SOW they wrote,

·        preliminary annotated SRS,

·        final SRS,

·        group Cost Model evaluation, and

·        evaluation of Mate Group SRS and Cost Models. 



In addition, each person in class will be required to do an evaluation of the other members of their group. The format of this is contained in a separate handout.  This evaluation will be private.  It should be included in a sealed envelope with student signature across flap as part of the final package.


Two exams:  The first will be in-class and will cover Systems Definition.  The second will be a take home consisting of individual running of cost models.



Week 1>

21 January

¨       Background; Introductions

¨       Groups:  Form Groups, Work on SOW




Week 2>

28 January

¨       Lecture: Requirements Engineering Processes [

¨       Groups:  Work on SOW




Week 3>

4 February

¨       Lecture: Requirements Elicitation, Analysis,Validation [

¨       Groups:  Work on SOW




Week 4>

11 February

¨       Lecture: Requirements Management, Methods [

¨      Groups: SOW (soft and hardcopy) due to professor




Week 5>

18 February

¨       Presentation by past students of SYST510 - from Fall 2003

¨       Groups: SOW returned; Mate Group assignments given; Bring copy of SOW to class to give to your Mate Group




Week 6>

25 February

¨       Lecture: Non-Functional Requirements




Week 7>

3 March

¨       Lecture: Interactive System Specification, Case Study

¨       Groups: Requirements elicitation & SRS writing




Week 8>

10 March

¨       Spring Break – no class




Week 9>

17 March

¨       In-class Test Number 1




Week 10>

24 March

¨       Lecture: Cost Modeling

¨       Groups: Preliminary SRS due to professor (soft and hardcopy)




Week 11>

31 March

¨      Guest Lecture: Ali Gurbuz demonstration of cost models to be used in the class assignment

¨      Groups:  Preliminary SRS returned; SRS revision and cost models

¨      Take-home Test Number 2 (covers Cost Modeling): Final Test Sheet handed to students

Week 12>

7 April

¨      Take-home Test Number 2: Individual Cost Models Due




Week 13>

14 April

¨      Guest Lecture: Marcus Achiume, ViewSet

¨      Take-home Test Number 2: Individual Cost Models due (hard copy only)

¨      Groups: Exchange SRS and cost models with Mate Group; final presentation preparation and evaluation of mate group SRS & cost models




Week 14>

21 April

¨      Student group presentations of final SRS and cost model




Week 15>

28 April

¨      Student group presentations of final SRS and cost model

¨      Group Deliverables Due:  to include SOW and Evaluation for each project from Users Group as well as SRS, Cost Model, and Final SRS for each project from Requirements Group