SlideServe
Télécharger Obtenir Pro
Menu
Accueil Pro
Préférences
ApparenceLight Aide et commentaires
© SlideServe · v2026

Specifications

gage avatar
gage
21 diapositives · 432 Views · Sep 30, 2014

Specifications. Specification document must be clear, complete and correct. The Document. Specifications document must clearly outline the constraints of the proposed system including restrictions on hardware, portability, reliability, timing and other resource usage issues.

Specifications - slide 1
01 / 21Specifications
1 / 17

Télécharger la présentation

Specifications
Une image / un lien ci-dessous est fourni (tel quel) pour télécharger la présentation

Politique de téléchargement : le contenu du site vous est fourni TEL QUEL pour votre information et votre usage personnel ; il ne peut être vendu, concédé sous licence ni partagé sur d’autres sites sans l’accord de son auteur.Le contenu vous est fourni TEL QUEL, pour votre information et votre usage personnel uniquement. Téléchargez la présentation en cliquant sur ce lien. Lors du téléchargement, si vous ne parvenez pas à télécharger une présentation, l’éditeur a peut-être supprimé le fichier de son serveur.Pendant le téléchargement, si vous ne parvenez pas à obtenir une présentation, le fichier a peut-être été supprimé par l’éditeur.

F I N

Plus de contenu associé

Transcription de la présentation

  1. Specifications Specification document must be clear, complete and correct Software Engineering - Specifications

  2. The Document • Specifications document must clearly outline the constraints of the proposed system including restrictions on hardware, portability, reliability, timing and other resource usage issues Software Engineering - Specifications

  3. Presentation of Specifications • Informal Techniques • Semi-Formal Techniques • Formal Techniques Software Engineering - Specifications

  4. Informal Techniques • Uses natural languages e.g. Spanish, English • Attempts to express what system will do when completed • Requires good grammatical skills • Contains a level of ambiguity Software Engineering - Specifications

  5. Semi-Formal Techniques • Seeks to remove ambiguity found with informal techniques • Seeks to be highly expressive • Seeks to be clear and logical to both developer and client representatives • Uses Diagrams Software Engineering - Specifications

  6. Data Flow Diagrams • Pictorial representation of all aspects of logical data flow • Uses predefined symbols to express the movement of data in a system • Cannot express all aspects of system • Developed iteratively Software Engineering - Specifications

  7. DFD Symbols • External Entity • Process • Data store • dataflow Software Engineering - Specifications

  8. Data Flow Diagrams • It essentially shows the logical data flow of a given process. • Lets look at few examples, which together demonstrate the uses and various levels of abstraction that can be achieved using DFDs. • First example: • data flow diagram for specifying the expression (a + b) * (c + a * d). Software Engineering - Specifications

  9. User b a d c + * + * Display Screen Example #1 Software Engineering - Specifications

  10. Example #2 • A software store purchases commercial off-the-self (COTS) software from various suppliers and resells them to the public. The store offers credit to institutions, corporations, and some individuals. After several years of good financial returns management has decided to fully computerise the company’s manual operation. Software Engineering - Specifications

  11. 1st Refinement DFD for the Software store Example #2: First Refinement Software Engineering - Specifications

  12. 2nd Refinement DFD for the Software store Example #2: Second Refinement Software Engineering - Specifications

  13. Example #2: Third Refinement Software Engineering - Specifications

  14. Entity-Relationship Modelling • Technique which allows relationships between data items to be expressed • Relationships may be one-to-one, one-to-many or many-to-many • Used primarily in the design of databases Software Engineering - Specifications

  15. Formal Techniques • Rely on mathematical sophistication • Includes finite state machines, petri nets and formal languages such as Z and VDM. • Requires high level of mathematical training to use Software Engineering - Specifications

  16. Informal techniques are easy to use and understand by client Formal techniques are highly expressive and correctness can be proved using maths. Informal techniques may be ambiguous, lack clarity of formal techniques Formal techniques are hard to learn, client may have difficulty grasping concepts Pros & Cons of techniques Software Engineering - Specifications

  17. Pros & Cons Cont’d • Many times the technique used will depend on the ability of client to understand the technique • For a client not having persons with a formal (maths) background, informal or semi-formal approaches may be the only viable ones. Software Engineering - Specifications

  18. Testing during specifications • These have been mentioned before, namely… • Walkthrough of specification document • Inspections process • Use of correctness proving (where formal technique is used) Software Engineering - Specifications

  19. Software Tools • Graphical tool – to construct diagrams, charts, drawings etc. • Data Dictionary(DD) tool – to store relationships between attributes • Combo Graphical/DD tool Software Engineering - Specifications

  20. Useful Metrics – pt. A • Number of pages in specification document. This allows comparison with past documents to give a sense of the scale of the current product being developed • Rate at which faults are found may also indicated how good spec. team is Software Engineering - Specifications

  21. Useful Metrics – pt. B • Number of potential files, processes, components etc. can also preview the eventual effort required. Software Engineering - Specifications