ADAMA SCIENCE AND TECHNOLOGY UNIVERSITY

SCHOOL OF ELECTRICAL ENGINEERING AND COMPUTING

DEPARTMENT OF SOFTWARE ENGINEERING

SOFTWARE REQUIREMENT ENGINEERING ASSIGNMENT

SECTION: 2

NAME ID NO

1. EFREM MELAKU ……………………………...……. UGR/22651/13

2. EGNUMA GABISA ……………………………………UGR/23003/13
3. NIGUSIE BEKELE …...………………………………. UGR/22627/13
4. LETI TAREKEGN …………………………………UGR/22860/13
5. LIDIYA MULACHEW ………………………………. UGR/23156/13
6. ROZA MEKETE ……………………………………… UGR/23406/13

SUBMITTED TO: Mr.

 1. Assume “CBE has decided to leverage IT for automating several of the business
processes. The aim of this proposed banking system is to create a paperless bank there by
moving towards e-banking. Win Soft, a newly established software company has the
vision of providing software solutions in the financial sector. Managing Director (MD) of
CBE bank has approached Win Soft for the computerization of the bank so that there is
no more manual way of doing transactions in any of its branches. As part of automation,
the CBE bank users are to be provided with ATM facility, e-banking facility over internet
and phone banking facility over land lines and cellular networks. Win Soft is doing such
a project for the first Time. Requirements development team in Win Soft has planned for
carrying out the requirement elicitation for this project” In the context of the case study,
for the following scenarios identify the most appropriate requirements elicitation
techniques (Brainstorming, Workshops, Questionnaire, Task Analysis, Observation,
Prototyping, Scenario identification).

Scenario Requirement Elicitation Techniques

Interrogative conversation with manager, Brainstorming
cashiers, clerks and other staff for arriving
at the requirement for automating
transaction
Formal and planned requirement discussion Workshops
in a conference room to conduct among
managers of diversified branched facilities
by anchor
Survey form circulated among the users Questionnaire
(account holders) who visit the bank to ease
their interactions with bank
Analysis for understanding mode of Task analysis
transactions checks, cash etc.
Ethnographers deployed for understanding Scenario identification
the user’s interaction with bank officials
UI design of e-banking portal, ATM, Prototyping
Computer Systems
Understanding the process involved in each Observation
transaction like withdraw, deposit, fund
transfer etc.

2. What is the difference between SRS document and design document? What are the
contents we should contain in the SRS document and design document?

SRS document
• Is about "what is needed" i.e., what software should do!
• Lists software requirements for a software application.
 • It is generally created by the Business Analyst or Product Manager.
• It outlines what the software should do, how it should behave, and any constraints or
limitations that it must adhere to.
• Defines the customer’s requirements in terms of Functions, performance, external
interfaces and design constraints.
SRS document Includes:
• Functional Requirement
• Nonfunctional Requirement
• User
• Interface
• System

Design Document
➢ Is about how Developer will achieve specified SRS
➢ Lists the technical design and more technical details of a software application.
➢ It is created by developer after feature or the application is developed.
➢ It outlines how the software will be implemented, including the specific algorithms, data
structures, and interfaces that will be used.
➢ The Design document is typically created after the SRS document, and is used as the
basis for the coding, testing, and maintenance of the software.
Design Document Includes:
➢ E-R Diagrams
➢ Data flow diagrams
➢ Data Dictionary

3. Mention at least two latest Requirements Management Tools? Explain in detail

about the features and in which application domain/industry can be used?

Requirements management tools are software applications that facilitate the process of
gathering, documenting, analyzing, verifying, prioritizing and approving the requirements of a
product.

Jama RM Tools
Provides the leading platform for requirements, risk, and test management. Jama Connect is a
requirements management tool aimed at teams that create complex software, systems and
products. It allows users to store and manage their requirements in a central database while
supporting numerous methodologies and disciplines.

The industries in which Jama can be used are the following:

❖ Information Technology and services

❖ Computer software
❖ Aviation and Aerospace
❖ Telecommunications
❖ Automotives

Jama Features

o Accurately capture and communicate requirements, goals, progress, and

interdependencies throughout the development process.
o End-to-end live traceability of people, data, and processes.
o It offers Live Traceability, Workflow Management, Real-time Collaboration, Test
Management and Bug Tracking.
o Seamlessly integrates with Jira, Azure DevOps, Bugzilla, TestRail, and Vector.
o You can Import and Export Data from Excel and Word.

Jira Software
Jira Software is a powerful and well-known software development. It is a software development
tool aimed at agile teams, with several features relating to requirements management. It offers a
centralized space for the organization of requirements and lets users translate requirements into
actionable specifications.

Jira features

• It offers Live Traceability, Workflow Management, Real-time Collaboration, Test

Management and Bug Tracking
• Ready-made templates for Agile, Scrum, bug tracking, and more
• Scum board for easy requirements management planning, tracking, and analyzing
requirements
• Customizable workflows
• It allows measuring performance in different ways for quick overview and pre-defined
report

The industry in which Jira can be used are the following:

 ✓ DROPBOX
✓ DELTA
✓ SAMSUNG
✓ COCA-COLA
✓ HITACHI and so on.

4. What are the purposes of Data Flow diagrams and Entity-Relationship diagrams?
Give an example diagram of each? (Use your project to give an examples)
Data Flow Diagram maps out the flow of information for any process or system. It uses defined
symbols like rectangles, circles and arrows, plus short text labels, to show data inputs, outputs,
storage points and the routes between each destination.

Data Flow Diagram is a diagrammatic representation of the information flows within a system
showing
• How information enters and leaves the system
• What changes the information
• Where information is stored

The purpose of a DFD

• To show scope and boundaries of the system

• To show that the whole system has been considered
• May be used as communication tools between system analyst and any person who
plays as part in system
• To act as starting point for redesigning a system

Examples of Data Flow Diagram for Online Bookstore (Our project)

0-Level DFD

Books & other Order receipt &

details confirmation
Online Book
Admin User
Store
Order & reports Personal Details
& Select
product
Entity-Relationship diagrams Simply stated the ER model is a conceptual data model that
views the real world as entities and relationships. A basic component of the model is the Entity-
Relationship diagram which is used to visually represent data objects. Since Chen wrote his
paper the model has been extended and today it is commonly used for database.

The purpose of Entity-Relationship diagrams

▪ To Gathering Requirements

▪ To Maintaining and Modifying a Database

▪ Assist the Database Developer

Examples of ER Diagrams of Online Bookstore

ER Diagram
pin country
U_id
state

passwor
d city

name user

email
1 address
phone

Choo
se

B_na usern
me 1 m
B_subca Book_i
t d
b_id B_desc Cart_id
Bk_nam
e

M 1
Book Adds Cart
to

qty
B_publish
er
price amoun
Edition 1 t
1
page ISBN
Write
query
confir
ms

M query
1
Cart_i
orderID d

email
contact
order

con_id usern
Order_ m
date

amoun
t