Professional Documents
Culture Documents
Today: Requirements Specification Requirements tell us what the system should do not how it should do it. Requirements are independent of the implementation tools, programming paradigm, etc. However, the requirements are then analysed with the intended implementation methodology in mind.
Testing
Maintenance
1.10.2004 Software Engineering 2004 Jyrki Nummenmaa 1 1.10.2004 Software Engineering 2004 Jyrki Nummenmaa 2
Prototyping
Requirements spec. - V&V Design - V&V Quick Analysis & Design - V&V Implementation Quick Implementation - V&V - V&V Testing V&V
Maintenance - V&V
3
1.10.2004
Typical Documents
Basic textual document, e.g. according to the ANSI/IEEE Standard 830 will be discussed later. A conceptual model of the domain, which may be already available or built separately. A description of the processes, e.g. a data flow diagram. A textual description of the use cases will be discussed later.
Formal Languages?
Usually much too difficult to understand even for an above average user. You may be able to verify the system, but how can you verify the requirements? They are usually used for critical well-defined systems and/or concurrent processing, which is notoriously difficult to handle.
1.10.2004
1.10.2004
Graphical Languages?
Examples: - Entity-Relationship (ER) model for conceptual description - Data Flow diagrams for process description Simple languages (like the above) work well in practice In requirement specification, they should be used to model the application domain and the processes.
1.10.2004
1.10.2004
An Alternative Template
Go to Pressmans books web pages (http://www.pressman5.com) and from their choose professional resources and then http://www.rspa.com and from there you can find work product templates. The one we are looking for is called System specification. Ok, you can go to rspa pages directly as well, but it may be a good idea to check up pressmans pages as well.
1.10.2004
13
Documenting a solution rather than the problem - If the users know some information technology, they want to start solving the problem as they express it. - Many formal (also graphical) methods tend to direct the process into this. Unrealistic requirements - Although we model the problem rather than the solution, it is good to have some idea of what is possible.
1.10.2004 Software Engineering 2004 Jyrki Nummenmaa 16
1.10.2004
17