System Analysis And Design For Waiters On Call Meal-Delivery System

Reflection on System Requirements Modelling

System Analysis & Design is one of the most significant aspects of the system development projects. There are several concepts that are defined under system analysis & design. The application of these concepts shall be done to design and develop a flexible, scalable, and reliable system. I got an opportunity to apply these concepts and my understanding of the methods on Waiters on call meal-delivery system that was to be developed. The system required the automation of order recording, updating, payments, and delivery operations for the customers.

It was necessary to determine the methodology for software development to be used for the project. I analysed the several options present and found out that agile methodology for system development will be apt for this case (Altameem, 2015). I selected the methodology as adaptive environment will be created for system development for the creation of portable, scalable, accurate, high-on quality, and reliable system as per the requirements. Before beginning the practical execution, it was necessary to perform a background analysis and I analysed the system capabilities, the benefits that the system could provide, and the system modules. The information helped me to analyse the project requirements. The system analysis and design phase of the project includes requirements analysis as one of the primary tasks. The requirements for the system were identified as per the FURPS+ acronym. The functional specifications were first defined that covers the primary functionalities to be included in the system. There were also additional requirements in the form of non-functional requirements that were to be covered to ensure enhanced user experience (Juric and Kuljis, 2010). These included usability, reliability, performance, and security requirements. I analysed the system and gathered information from several data sources to define all of these non-functional requirements for the system. There is different data collection techniques defined and I utilized them for system analysis and requirements analysis processes. Some of the techniques that I used were interviews, observations, and surveys.

System analysis and design concepts also involve various use case modelling (UML) concepts so that the in-depth details of the system can be understood and put forward. It is necessary that the analysis and designing of the system is adequately done so that the tasks for the development and deployment teams simplifies. The UML concepts under system analysis and design provide the ability to graphically represent the system requirements and specifications (Misbhauddin and Alshayeb, 2013). I developed a number of such modelling diagrams for the case provided so that the adequate understanding of the system could be achieved. There was several use cases involved with the restaurant service management system that had to be developed. The two techniques that can be used to identify the use cases are user goal technique and event decomposition technique. I made use of the event decomposition technique to identify the use cases. In this technique, I listed down all the events that could take place under restaurant service management system. I then allotted a use case name to each event that I had identified. There were different events that I identified, such as external events, temporal events, state events etc. In the use case diagram, the users are represented as the actors and the use cases are the actions that these users perform. The three actors in the case were customer, employee, and driver. I mapped the relationship between these actors and their respective actions on the use case diagram.

Apart from the user case diagram, there are several other diagrams defined under UML. Activity diagram is one such diagram that I developed to further understand the system specifications and modules. The system processes in this diagram were plotted in the form of the activities. These activities were represented under each user of the system and the connections were also depicted (Bhuiyan, Haque and Shabnam, 2018).

The project provided me with an opportunity to apply my knowledge and skills on system analysis and design concepts. It also provided me with a chance to improve upon my weaknesses. For instance, I had theoretical knowledge of the event decomposition technique but did not get a chance to apply it practically. The project gave me an opportunity to practically implement this technique. There were certain issues that I experienced with the technique initially but later got success with it. Apart from the concepts that I used and applied, there are abundant of other concepts that may be applied as per the requirements of the system (Muhairat, 2010). For instance, data flow diagrams, entity relationship diagrams, sequence diagrams etc. can also be plotted.  

Use Case Diagram 

 

 

References

Altameem, E. (2015). Impact of Agile Methodology on Software Development. Computer and Information Science, 8(2).

Bhuiyan, M., Haque, F. and Shabnam, L. (2018). Integration of Organisational Models and UML Use Case. Journal of Computers, 13(1), pp.1-17.

Juric, R. and Kuljis, J. (2010). Engineering Requirements Through Use Cases in Complex Business Environment. Requirements Engineering, 4(2), pp.65-76.

Misbhauddin, M. and Alshayeb, M. (2013). Extending the UML use case metamodel with behavioral information to facilitate model analysis and interchange. Software & Systems Modeling, 14(2), pp.813-838.

Muhairat (2010). UML Diagrams Generator: A New CASE Tool to Construct the Use-Case and Class Diagrams from an Event Table. Journal of Computer Science, 6(3), pp.253-260.