Background of T
Background of T
Functional requirements describe the interactions between the system and its
environment independent
of its implementation. The environment includes the user and any other external
system with which the
system interacts. Functional requirements that must be included in the system are:
⚫ The system allows the admin login by their own username and password, create user
account, active and deactivate users and logout the system.
The system allows the manager login by their own username and password, register
customers and employees, generate reports (daily, weekly, monthly and annually),
view customers and employees profiles, view comments, view order historics, make
backup and recovery and logout the system
The system allows the casher login by their own username and password, manipulates
daily food menus, generate reports (daily, weekly, monthly and annually), view
order histories of each orders and logout the system.
The system allows the kitchen login by their own username and password, notify
daily food menus to the casher, and generate reports (daily, weekly, monthly and
annually) and logout the system
The system allows the waiter login by their own username and password, view order
histories deliver the food and logout the system.
also the user can navigate easily from one page to the other. Reliability: the
system achieve reliability by
Robustness: no failure at all during work. ✓ Safety: is safe since no data will be
lost.
Performance: since we are using best algorithms the performance of the system is
high. Response time: for any request the response time is less than 5 seconds.
Accuracy: the system will do what the user ordered only.
✓ Adaptability: the system can add any features at any time since it is designed by
inheritance.
Portability: since we are using machine independent programming language the system
itself machine independent or portable.
Class diagrams are used to describe the structure of the system. Classes are
abstractions that specify the common structure and behavior of a set of objects.
Objects are instances of classes that are created, modified, and destroyed during
the execution of the system. An object has state that includes the values of its
attributes and its links with other objects. Class diagrams describe the system in
terms of objects, classes, attributes, operations, and their associations
Analysis Modeling
* Sequence Diagram
Sequence diagrams show the interaction between participating objects in a given use
case. They are helpful to identify the missing objects that are not identified in
the other analysis object models.