Characteristics of good SRS( Software Requirement Specification).

Characteristics of good SRS are:-

 • Correct: Every requirement given in SRS is a requirement of the software


• Unambiguous: Every requirement has exactly one interpretation


• Complete: Includes all functional, performance, design, external interface requirements, the definition of the response of the software to all inputs.


• Consistent: Internal consistency.


Ranked importance: Essential vs. desirable.


• Verifiable: A requirement is verifiable if and only if there exists some finite cost-effective process with which a person or machine can check that the SW meets the requirement •


• Modifiable: SRS must be structured to permit effective modifications (e.g. don't be redundant, keep requirements separate)


• Traceable: The origin of each requirement is clear.


Comments

Popular posts from this blog

Suppose that a data warehouse for Big-University consists of the following four dimensions: student, course, semester, and instructor, and two measures count and avg_grade. When at the lowest conceptual level (e.g., for a given student, course, semester, and instructor combination), the avg_grade measure stores the actual course grade of the student. At higher conceptual levels, avg_grade stores the average grade for the given combination. a) Draw a snowflake schema diagram for the data warehouse. b) Starting with the base cuboid [student, course, semester, instructor], what specific OLAP operations (e.g., roll-up from semester to year) should one perform in order to list the average grade of CS courses for each BigUniversity student. c) If each dimension has five levels (including all), such as “student < major < status < university < all”, how many cuboids will this cube contain (including the base and apex cuboids)?

Suppose that a data warehouse consists of the four dimensions; date, spectator, location, and game, and the two measures, count and charge, where charge is the fee that a spectator pays when watching a game on a given date. Spectators may be students, adults, or seniors, with each category having its own charge rate. a) Draw a star schema diagram for the data b) Starting with the base cuboid [date; spectator; location; game], what specific OLAP operations should perform in order to list the total charge paid by student spectators at GM Place in 2004?

Discuss classification or taxonomy of virtualization at different levels.