Lecture-06

Lecture-06 - CEN 4021 CEN 4021 Software Engineering II...

Info iconThis preview shows pages 1–10. Sign up to view the full content.

View Full Document Right Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon

Info iconThis preview has intentionally blurred sections. Sign up to view the full version.

View Full DocumentRight Arrow Icon
This is the end of the preview. Sign up to access the rest of the document.

Unformatted text preview: CEN 4021 CEN 4021 Software Engineering II Software Engineering II Instructor: Masoud Sadjadi http://www.cs.fiu.edu/~sadjadi/ sadjadi@cs.fiu.edu Software Project Planning ( P OMA) Overview of goals and measurements 6 Lecture CEN 4021: Software Engineering II Acknowledgements Acknowledgements Dr. Onyeka Ezenwoye Dr. Peter Clarke 2 6 Lecture CEN 4021: Software Engineering II Agenda Agenda Software Project Planning ( P OMA) Overview of goals and measurements 6 Lecture CEN 4021: Software Engineering II Overview of Goals and Measurements Overview of Goals and Measurements During the planning phase the goals for and measurements of, the key attributes of the product and services are determined. Many of the goals for the system are deduced from the functional and nonfunctional requirements. 6 Lecture CEN 4021: Software Engineering II Attributes of good software Attributes of good software 6 Lecture CEN 4021: Software Engineering II What are the attributes of good software? software? The software should deliver the required functionality. Maintainability Software must evolve to meet changing needs; Dependability Reliable, Secure, Safe, trustworthy; Efficiency Software should not make wasteful use of system resources; Usability Used without undue effort . Appropriate interface Good documentation 6 Lecture CEN 4021: Software Engineering II Functional and non-functional Functional and non-functional requirements requirements Functional requirements Statements of services the system should provide, how the system should react to particular inputs and how the system should behave in particular situations. Describe interaction between the system and its environment. Non-functional requirements constraints on the services or functions offered by the system such as timing constraints, constraints on the development process, standards, etc. Describes aspects of the system that are not directly related to the functional behaviour. 6 Lecture CEN 4021: Software Engineering II Functional requirements Functional requirements Describe functionality or system services. Depend on the type of software, expected users and the type of system where the software is used. Functional user requirements may be high-level statements of what the system should do but functional system requirements should describe the system services in detail . 6 Lecture CEN 4021: Software Engineering II Non-functional requirements Non-functional requirements These define system properties and constraints e.g....
View Full Document

This note was uploaded on 08/29/2011 for the course CEN 4021 taught by Professor Staff during the Spring '08 term at FIU.

Page1 / 28

Lecture-06 - CEN 4021 CEN 4021 Software Engineering II...

This preview shows document pages 1 - 10. Sign up to view the full document.

View Full Document Right Arrow Icon
Ask a homework question - tutors are online