Scribd
Upload
21 views

Chapter 2

Uploaded by

Ayano Boresa
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
21 views

Chapter 2

Uploaded by

Ayano Boresa
Copyright
© © All Rights Reserved
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 8

HAWASSA UNIVERSITY

Daye campus department of


computer science
Department of Computer Science: 3rd Year

Software Engineering

STORE RECORD MANAGEMENT SYSTEM

CHAPTER 2
Group members name and ID Number
1.

Submission date:-

Submitted to:-
Index

1. Overview of existing system


2. Overview of the proposed system
3. System Requirements
3.1. Functional Requirements
3.2. Non-functional Requirements
4. Actor identification
5. Use case identification

2
1. . Overview of existing system

3
2. Overview of the proposed system

4
3. System Requirement
3.1 Non-functional Requirement and Constraints
Nonfunctional (supplementary) requirements pertain to other information needed to produce the correct system
and are detailed separately. Constraints on the services or functions offered by the system such as
timing constraints, constraints on the development process, standards and etc.

 User interface: the system provides java user interfaces that are compatible with windows
platform.
 Hardware consideration:-the organization should have computers having typical storage
capacity and processing speed.
 Error handling: our system handles error by showing the message” invalid input”
when
the user inters invalid input.
 Security: the system should have a security privilege that secures the system. And also
there must be a physical security that secures (especially) the server computer. That means
the server computer is only allowed for the server admin.
 Performance characteristics: the end user computer should have medium processor and the
server computer should have large processor. It’s measured by its speed of processor.
 Physical environment: The system needs good environment.
 Back up: The system should have back up using external hard disk. The backup is taken
weekly.
 Availability-The system should be available all the time
3.2. Functional Requirement

Functional Requirements are those that refer to the functionality of the system, i.e., what services it will
provide to the user. Statements of services the system should provide how the system should
react to particular inputs and how the system should behave in particular situations.

The system would be able to register the received materials.

 The system would be able to register all stock.


 The system also have to record all sales.
 The system would be able to control the availability of good & items.
 The system would be able to search and update the material information when it is
needed.
 The system would be able to notice for refilling stock.
 Record items and materials when items and materials are received.
 Change Status of items and materials when items and materials are used.
 The system should generate timely or year report about the allocation of resources.
 The system should store all the data related with all the tasks performed into a database.

5
4. Actor identification

6
5. Use case identification

7
8

You might also like