Project on Requirements Elicitation, Class & Statechart Diagrams

This software engineering project delves into the critical aspects of requirements elicitation and validation, emphasizing the iterative nature of the process and the importance of stakeholder involvement, documentation, and the use of scenarios and use cases. The project outlines the process of requirements elicitation, including various techniques such as interviews and documentation. It specifies requirements for a browser tab tool, covering functionalities such as text input, conversion of tabs to spaces, and vice versa, along with considerations for user-friendliness, compatibility across browsers, and concurrency. Additionally, the project presents a class diagram defining classes like Sales, Rent, Property, and Owner, along with their attributes, and a statechart diagram illustrating system states. The project concludes with a list of cited references. This assignment provides a comprehensive overview of key software engineering principles and practical applications.

Student Name:
Assignment:
Lecturer:
Date:
Assignment

Table of Contents
Question 1: Requirements Elicitation..........................................................................................................3
Question 2: Class Diagram...........................................................................................................................5
Question 3: Statechart Diagram..................................................................................................................6
References...................................................................................................................................................7

Question 1: Requirements Elicitation
1. Iteration of requirements elicitation and validation
Requirements elicitation and validation process are iterative process as the requirements keep on
changing. The team is composed of various people which may include end users, managers,
engineers, domain experts and trade unoins. The stakeholders most of times do not know what
they want and thus cant express the requirements in their own words. Requirements for various
stakeholders are conflicting with some of stakeholders being influence by various political and
organizational factors changes as they come in with new requirements and thus iterations are
needed (Rokke, 2017).
2. Requirement documentation
Documentation is a very improtant of requirement elicitation and validation process. Some
process stakeholders often think the documentation as a risk reduction strategy. It safely stores
all the proposed system requirements by every stakeholders for every stakeholders as it waits for
validation (Stroud, 2017). Documentall al requirements is important in subsequent stages as it
used for future reference so as to achieve the relevant goals.
3. Scenerios and use case
In a requirements document use cases shows actor and flow taken by various actors to perform
various functionalities. The functionalities are grouped as a set of use cases that account for a
particular scenario. A scenario shows a situation with a single or multiple actors who take a
specific functionality to solve the scenario (Malan, 2011). Use case and scenario differ in
perspective as use case is more granular than scenario.
4. Interview question
When interviewing an employee, it is important that the interviewer prepares a set of questions
and stick those question during interviews. This questions allows the interviewer avoid personal
biases, collect intended feedback and control information confidentiality (Williams, 2014). During
interviews personal biases can blur judgements and may also result to recording of wrong
feedback that do not reflect what the interviewee said.
5. Requirement goals and specifications
Requirements specification shows how the proposed product will entirely function from client’s
perspective. Requirements specification do not care about how it will be implementation but
emphasizes on what is needed. Requirements goals takes care of internal implementation and it
specifies how the system will be implemented to meet the client requirements (Torrecampo, 2017)

6. Requirements
Requirements Functionality
a. Browser Tab tool The browser tab tool should be able to allow
input inform of text. The tab tool should be
able to accept user text document in plain
text. The tools should analyze the document
text to find tabs which are then converted to
spaces. Also the text spaces should be
converted to tabs. The conversion will involve
changes f tab size that reflect the size of a tab
or space of the converted text.
b. Intuitive and Interactive tab tool The tab should be highly interactive so as it is
easy for users to use. In the tab it should have
guidance materials such as placeholder to
guide user input
c. Compatibility The website will be tested with various
browsers to test behavior. The functionality
should made similar across all browsers
d. Concurrency Being a system deployed on the cloud,
various users should be able to access the
website from different locations and use it at
the same time with decline in performance,
availability or reliability. The website should
allow distributed usage and synchronize all
the data captured

Question 2: Class Diagram
Classes and their attributes
1. Sales
Sale id
Price
deposit paid
settlement date
2. Rent
Property id
Rental length
payment method
3. Property
Property id
property name
maintenance description (report)
4. Owner
Owner id
5. Agent
Employee id
Job description
inspection report

Question 3: Statechart Diagram

References
Malan, R. (2011). Functional Requirements and Use Cases. Architecture Resources. [Online]
Bredemeyer Consulting. Available at: http://www.bredemeyer.com/pdf_files/functreq.pdf
[Accessed 22 Aug. 2017].
Røkke, J. (2017). Requirement Elicitation and Validation By Prototyping And Demonstrators:
User Interface Development In The Oil And Gas Industry. [online] World Scientific
Publishing Company. Available at:
http://www.worldscientific.com/doi/abs/10.1142/S179396661100031X [Accessed 22 Aug.
2017].
Stroud, J. (2017). Business Requirements Document: a High-level Review. [online]
Isixsigma.com. Available at: https://www.isixsigma.com/implementation/project-selection-
tracking/business-requirements-document-high-level-review [Accessed 22 Aug. 2017].
Torrecampo, D. (2017). ProjectManagement.com - System Requirements Specification. [online]
Projectmanagement.com. Available at:
https://www.projectmanagement.com/deliverables/238236/System-Requirements-
Specification [Accessed 22 Aug. 2017].
Williams, G. (2014). Interview: Any question you like. Physics Education, 49(4), pp.448-450.