0% found this document useful (0 votes)
80 views8 pages

Store Record Management System Overview

Uploaded by

Ayano Boresa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
80 views8 pages

Store Record Management System Overview

Uploaded by

Ayano Boresa
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd

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

Common questions

Powered by AI

The proposed system manages data backup by using external hard disks, with backups taken weekly . This strategy is critical for system reliability as it ensures data recovery in case of data loss due to system failures or other unforeseen events. Regular backups safeguard against data corruption and loss, maintaining data integrity and availability even in adverse conditions.

Use case identification is critical in the proposed system's development because it defines the system's functionality in terms of user interaction, ensuring all user requirements and expected system behaviors are accounted for. It helps in creating a clear blueprint for developers to design system features accurately, addressing all possible scenarios users might encounter. This ensures a comprehensive and user-centered system design .

The primary actors in the proposed system include system administrators, users involved in data entry and retrieval, and potential external auditors. Administrators are responsible for managing system settings, ensuring data security, and overseeing system maintenance. Users perform daily operations like data entry, sales recording, and stock monitoring. External auditors may interact with the system to assess its compliance and performance .

The proposed system ensures continuous availability by being structured to operate uninterrupted at all times . Challenges that might arise include handling system downtime due to maintenance or unexpected technical issues. Ensuring system resilience against unexpected outages and integrating effective load balancing might be necessary to meet this requirement, adding complexity to the system's infrastructure and maintenance.

The functional requirements of the proposed system enhance inventory management by enabling the registration of received materials and the entire stock, recording sales, monitoring item availability, and notifying for stock refilling. This systematic approach allows for efficient tracking and updating of material information and generates timely resource allocation reports. These capabilities provide a more organized and responsive inventory management system compared to the existing system .

The proposed system handles errors by displaying an 'invalid input' message when users enter incorrect data. This approach provides immediate feedback to users, allowing them to correct their inputs in real-time, thus minimizing potential disruptions in workflow and enhancing the overall user experience. By addressing errors promptly, the system can maintain consistent performance and user satisfaction .

The non-functional requirements for the proposed system include user interface compatibility with Windows, hardware specifications such as storage and processing speed, error handling which notifies users of invalid inputs, and security protocols including restricted access to the server computer. Additionally, the system demands good physical environment conditions, weekly data backup procedures using external hard disks, constant availability, and performance standards that involve medium processors for end-user computers and large processors for servers . These components collectively ensure system reliability, efficiency, and protection against unauthorized access and data loss.

Physical and data security measures in the proposed system include restricting server computer access exclusively to the server administrator and implementing security privileges to safeguard system data . This ensures that only authorized personnel can manage and maintain the server, reducing the risk of data breaches and unauthorized data access. These measures are crucial for maintaining the confidentiality, integrity, and availability of sensitive system data.

The proposed system specifies performance characteristics such as the requirement for medium processors on end-user computers and large processors on the server computer . These specifications ensure that the system can handle processing demands efficiently, providing fast data access and transaction processing. This setup enhances operational efficiency by minimizing response times and maximizing processing speeds, crucial for a system that requires real-time data handling.

The proposed system ensures user accessibility and ease of use by providing Java-based user interfaces compatible with Windows platforms . This approach aligns with most users' operating system preferences, thereby simplifying access to the system. By ensuring consistency and familiarity in interface design, the system enhances user interaction and reduces the learning curve, ultimately leading to increased efficiency and user satisfaction.

You might also like