Information & computer Sciences Department			SWE 214 Intro. to Software Engineering Fall 2006
Home	What's New	Assignments	Quizzes	Exams	Slides	Links

Description

The course covers software engineering process models, requirements engineering process, and system models. More emphasis is put on methods, tools, notations, and verification and validation techniques for the analysis and specification of software requirements. The students will be introduced to the principles of project management. They will be exposed to the use-case driven approach for developing softwares and will practice requirements engineering, systems modeling, object orientation paradigm and UML CASE tools within a teamwork environment. Here is the course syllabus.

Prerequisites

  ICS 201

Course Objectives

1.      To understand the role and scope of requirements engineering.

2.       To know and apply appropriate methods, techniques and tools to elicit, document and manage requirements.

3.      To be able to define a system that satisfies the requirements.

4.        To learn how to work in teams.

Course Learning Outcomes

After completion of this course, the student shall be able to:

1. Develop clear, concise, and sufficiently formal software requirements specifications based on the true needs of users and stakeholders.

2. Verify and validate software requirements.

3. Create a vision statement for a system and identify stakeholders.

4. Use appropriate CASE-tools for documenting software requirements.

5. Priorities and manage requirements and resolve any conflicting requirements.

6. Create a number of different UML models such as class model, use-cases, sequence diagram, activity diagram, and state charts.

7. Apply storyboarding to define a software features.

8. Be an effective member in software requirement team.

References

Requirements Engineering

• Suzanne Robertson and James Robertson, Mastering the Requirements Process, Addison-Wesley, 1999.
• Gerald Kotonya and Ian Sommerville, Requirements Engineering: Processes and Techniques, John Wiley, 1998. The book has an associated set of OHP Transparencies (Powerpoint 4) which may be downloaded from the Accompanying Website.
• Ian Sommerville and Pete Sawyer, Requirements Engineering: A good practice guide, John Wiley, 1997.  The Accompanying Website provides links to resources with information on requirements engineering.

UML

• Simon Bennet, John Skelton and Ken Lunn, UML, Schaum's Outline Series,  McGraw-Hill, 2001.
• Perdita Stevens and Rob Pooley. Using UML: Software Engineering with Objects and Components. Addison-Wesley, 2000.
• Sinan Si Alhir. UML in a Nutshell: A Desktop Quick Reference. O'Reilly, 1998.
• Sinan Si Alhir. Learning UML. O'Reilly, 2003.
• James Rumbaugh, Ivar Jacobson and Grady Booch. The Unified Modeling Language Reference Manual. Addison-Wesley, 1999.
• Martin Fowler, Kendall Scott: UML Distilled, Addison-Wesley 2000
• James Rumbaugh, et al: The Unified Modeling Language Reference Manual,  Addison-Wesley
• Ivar Jacobson, et al: Unified Software Development Process, Addison-Wesley
• Jos B. Warmer, Anneke G. Kleppe: The Object Constraint Language : Precise Modeling With UML, Addison-Wesley

Software Engineering

• Ian Sommerville, Software Engineering (7th Ed.)

Evaluation