Colegio de Dagupan

Masters in Information Technology

Software Requirements Specification

Finals Exam
SY 2018-2019

Test I. TRUE OR FALSE

Analyze the following statements then write TRUE if the statement is correct, otherwise, explain very
briefly why the statement is incorrect.

1. Requirements may be the basis for a bid of contract and may be the basis for the contract itself.
2. Requirements analysis provides software designer with a model of system information, function and
behavior.
3. Expect to do a little bit of design during analysis and a little bit of analysis during design.
4. Risk is a potential problem that might or might not happen.
5. Requirements focus on customer’s needs and problems, not on solutions.
6. Web development process must be Agile.
7. To be successful, users should acknowledge that administrators’ requirements are given priority.
8. Map out strategies and decide what you would like to achieve; what the other party wants to achieve and
how you will go about making all things happen.
9. The success of systems development lies in the hands of the systems analyst.
10. Let your heart dictate what problem needs to be solved.
11. Requirements negotiation enables a shared vision throughout the life cycle.
12. If risks become real, it is guaranteed that the project schedule will not be met and that costs will increase
exponentially.
13. Proactive risk strategy is better than the reactive risk strategy wherein solution will be laid when risk occurs.
14. Requirements cannot be managed effectively without traceability.
15. Negotiation may be needed when there are changes in requirements.

Test II. MULTIPLE CHOICE.

Write the letter most appropriate choice in the following statements.

16. The basic unit of analysis which is initiated by event occurring at specific time and place.
a. Events
b. Use case
c. Elementary business processes
d. Requirements

17. These are the activity that the system carries out, it also serves as the entry point into the modeling
process.
a. Events
b. Use case
c. Elementary business processes
d. Requirements

18. The set of work-related “things” in system component that have data representation within systems.
a. Problem domain
b. Event
c. Use Case
d. Entity
19. It is described to be a condition or capability needed by a user to solve a problem or achieve an objective.
a. Requirements
b. Requirements Inception
c. Requirements Engineering
d. Requirements Management

20. 8. The following models are used to describe system uses cases from various points of view except one.
a. use case diagrams
b. use case descriptions
c. activity diagrams
d. statechart diagrams

21. This refers to the line drawn around the entire set of use cases.
a. Actor
b. Relationship line
c. Automation boundary
d. Extension

22. Which is probably NOT true about building use cases?

a. Analysts are involved
b. Users are involved
c. Major processes are analyzed
d. Major costs are analyzed

23. What is probably NOT a part of a Use Case?

a. Number
b. Trigger
c. Major inputs
d. Statement of business value

24. The primary actor in a use case is generally:

a. An external user of the system
b. The Project Sponsor
c. The Champion
d. The Project manager
e. The Systems Analyst

25. A ‘temporal’ trigger might be which of the following:

a. A patient calls to make an appointment with a doctor
b. The human resources department needs a tax withholding form to be filled out by a new employee
c. The date changes to the first day of the month
d. A new shipping of goods arrives and needs to be added to the inventory

26. Which of the following is probably NOT a step for writing a use case?
a. Identify the use case
b. Identify the major steps within each use case
c. Identify elements within steps
d. Identify the analyst

27. Omar is an analyst building a use case. Which of the following project roles might be the most important
in terms of getting information about building the use case?
a. Users
b. Programmers
 c. Other analysts
d. Project Sponsor
e. Equipment vendors

28. Use cases are used to more fully delineate _____.

a. Resources used in the system
b. System boundaries
c. System proposals
d. System requirements
e. Data flows

29. Austin is a systems analyst. Which of the follow people might be the most valuable to him in developing a
use case for an accounts payable system upgrade?
a. Beth, a software vendor for Peachtree Accounting Software
b. Amy, a team manager in the accounts payable department
c. Lisa, the project manager for the project
d. Casey, a fellow analyst who is more experienced in making use cases
e. Bill, a Java programmer in the applications development area.

30. Destination would be described on a use case in which of the following areas?
a. Trigger
b. Major inputs
c. Major outputs
d. Primary actor
e. Importance level

31. The Major Inputs section of a use case describes their:

a. File structure
b. Cardinality
c. Modality
d. Source
e. Destination

32. It is described to be a condition or capability needed by a user to solve a problem or achieve an objective.
a. Requirements
b. Requirements Inception
c. Requirements Engineering
d. Requirements Management
e. All of the Above

33. Which of the following is not true about requirements management?

a. It is concerned in managing the relationships between requirements.
b. It is tasked in bridging the gap between system requirements engineering and software design.
c. Requirements are scheduled.
d. It involves the collection, storage and maintenance of large amounts of information.

34. Which of the following statements is true to requirements negotiation?

a. It is otherwise known as conflict resolution.
b. The process that addresses problems with requirements where conflicts remain constant
c. This process is sometimes viewed as one of the priorities of requirements specification
d. Conflicts are reflected into the system models.

35. Which of the following is the most significant process in requirements negotiation?
 a. The systems analyst sets the common objectives.
b. Conflict is recognized.
c. Settlement of conflicts wherein parties may end up sacrificing their objectives in order to give way
to the priority requirements.
d. Conflicts should be thoroughly discussed, its pros and cons are all mapped.

Test III. ESSAY.

1. Discuss briefly five of the top ten project success factors.25

3. Discuss the phases of SDLC and relate to Software Requirements Specification. 20 pts
4. Differentiate the following:20
a. user and system requirements
b. functional and non-functional requirements
5. List functional and non-functional requirements for an ATM system. 10
a. 5 functional requirements
b. 5 non-functional requirements (categorize)
6. Differentiate the interview, questionnaire and documents analysis in terms of the following: 15 pts
a. objective
b. breadth of analysis
c. advantage/disadvantage

Test IV. APPLICATION. 40 pts

Draw a use case diagram and class diagram for the following description that identifies the business
need for a simple university library system.

This case is a simplified (initial draft) of a new system for the University Library. Of course, the library
system must keep track of books. Information is maintained about both book titles and the individual
book copies. Book titles maintain information about title, author, publisher, and catalog number.
Individual copies maintain copy number, edition, publication year, ISBN, book status (whether it is on
the shelf or loaned out), and date due back in.
The library also keeps track of patrons to the library. Since it is a university library, there are several
types of patrons, each with different privileges. There are faculty patrons, graduate student patrons,
and undergraduate student patrons. Basic information about all patrons is name, address, and
telephone number. For faculty patrons, additional information is office address and telephone
number. For graduate students, information such as graduate program and advisor information is
maintained. For undergraduate students’ program and total credit hours are maintained.
The library also keeps information about library loans. A library loan is a somewhat abstract object.
A loan occurs when a patron approaches the circulation desk with a stack of books to check out. Over
time a patron can have many loans. A loan can have many physical books associated with it. (And a
physical book can be on many loans over a period of time. Information about past loans is kept in the
database.) So, in this case, it is recommended that an association class be created for loaned books.
If a book is checked out that a patron wants, he/she can put that title on reserve. This is another
class that does not represent a concrete object. Each reservation is for only one title and one patron.
Information such as date reserved, priority, and date fulfilled is maintained. When it is fulfilled, the
system associates it with the loan on which it was checked out.
Patrons have access to the library information to search for book titles and to see whether a book is
available. A patron can also reserve a title if all copies are checked out. When patrons bring books to
the circulation desk, a clerk checks out the books on a loan. Clerks also check books in. When books
are dropped in the return slot, the clerks check them in. Stocking clerks keep track of the arrival of
new books.
 The managers in the library have their own activities. They will print out reports of book titles by
category. They also like to see (online) all overdue books. When books get damaged or destroyed,
they will delete information about book copies. Managers also like to see what books are on reserve.

To God be the glory!!

Prepared by:

Terry Ann C. Cayabyab, MAM, MIT

Associate Professor