View Module

An error occurred while attempting to get the requested module. Cannot open database "AspNetForums" requested by the login. The login failed. Login failed for user 'swenet'. at AspNetForums.Data.SqlDataProvider.GetRatingForUser(String username, Int32 parentID) at AspNetForums.Ratings.GetRatingForUser(String username, Int32 parentID) at SwenetDev.ModuleRatingsControl.getRatingForUser(String username, ModuleRatingInfo ratingInfo) at SwenetDev.viewModule.Page_Load(Object sender, EventArgs e)

General Information

Title Informal Requirements Modeling (REQ1)
Version Info Version 1 , submitted by sebern on 3/19/2004 at 12:00 AM
View Revision History
Module Identifier sebern.2004.1
Abstract This module is designed to introduce the analysis and specification of software requirements using informal techniques. It is intended as preparation for the introduction of formal methods of requirements analysis, specification, and verification. It might also be used as a separate exercise. This module minimizes the complexity of requirements elicitation by using an example that will already be familiar to most students.
Size Lecture: 2 hours
Exercise: 2 hours
Comments This module is appropriate for inclusion in a first course in software requirements or in a course that applies formal methods to the documentation and analysis of software requirements. The example used in the module exercise can also be used as a vehicle for work with formal specification and modeling, as in a related module introducing formal specification (REQ2).

SEEK Categories

  1. Requirements fundamentals (MAA.rfd)
  2. Requirements specification & documentation (MAA.rsd)
  3. Requirements validation (MAA.rv)


  1. Mark Sebern


  1. Proficiency in programming in a high-level language.
  2. Experience in the design of small software systems.

Learning Objectives

  1. Knowledge - Describe some difficulties in specifying software requirements.
  2. Analysis - Identify software requirements from a general system description, formulating questions to be addressed by a "client".
  3. Synthesis - Document software requirements in an informal specification.
  4. Evaluation - Identify difficulties encountered in analyzing and specifying software requirements.


  1. Techniques used in informal specification of software requirements.
  2. Analysis and informal specification of software requirements.
  3. Strengths and weaknesses of informal specifications.


  1. Informal specification exercise (HTML) (PDF) 0.00/5 [Rate Material]

  2. Teaching tips (HTML) (PDF) 0.00/5 [Rate Material]

  3. Key to informal specification exercise (HTML) 0.00/5 [Rate Material]

  4. Key to informal specification exercise (PDF) 0.00/5 [Rate Material]


See Also...

No alternate modules.

Other Resources

  1. Robertson S. and Robertson J. Mastering the Requirements Process. Addison-Wesley, 1999.
  2. Software Engineering Body of Knowledge (Link)


Number of Ratings:   1
Average Rating: 5 / 5
Current Rating Comments

Log in to rate this module.


Discuss this module in the forums.

Related Modules