Systems Design Report: Analysis and Design for CHEMEXEC Systems

This systems design report provides a detailed analysis and design for a new information system within the CHEMEXEC organization. The report includes several key components such as sequence diagrams for entering new orders, creating case manifests, and recording order fulfillment, as well as a class diagram illustrating the organizational structure. The deployment strategy focuses on a parallel deployment approach to minimize disruption, with considerations for end users, operational employees, and maintenance staff. Security measures are addressed through authorization and authentication techniques, including user ID verification and MAC address recognition. A database schema, presented as an entity-relationship diagram, is also included. The report concludes with a risk management section, identifying potential risks like implementation costs, project deadlines, and resource allocation, along with proposed countermeasures. The author reflects on their contributions to the project, including the creation of UML diagrams and assistance with the database schema and risk management components. The report references several academic sources to support its design and analysis.

Running head: SYSTEMS DESIGN REPORT
Systems Design Report Part B
Name of the Student
Name of the University

1SYSTEMS DESIGN REPORT
Table of Contents
1. Sequence Diagram:......................................................................................................................2
2. Class Diagram:............................................................................................................................5
3. Deployment:................................................................................................................................5
4. Security:.......................................................................................................................................6
5. Database Schema:........................................................................................................................7
6. Risk Management:.......................................................................................................................7
7. Reflection:....................................................................................................................................8
Bibliography:...................................................................................................................................9

2SYSTEMS DESIGN REPORT
1. Sequence Diagram:
Figure 1: Enter New Order Sequence Diagram

3SYSTEMS DESIGN REPORT
(Source: Created by Author)
Figure 2: Create Case Manifest Sequence Diagram
(Source: Created by Author)

4SYSTEMS DESIGN REPORT
Figure 3: Sequence Diagram of Record Order Fulfilment
(Source: Created by Author)

5SYSTEMS DESIGN REPORT
2. Class Diagram:
Figure 4: CHEMEXEC Organization Class Diagram
(Source: Created by Author)
3. Deployment:
The deployment of the new information system within CHEMEXEC has three audiences
such as the end user, operational employees and maintenance staff. The end users will be using

6SYSTEMS DESIGN REPORT
the GUI of the system to make use of system functions and features. On the other hand, the
operational employees will be running the application after it is in production. These audiences
are currently using an existing system within CHEMEXEC for a very long time. Thus parallel
deployment may be the best way of deploying the system. It will allow the organization to
switchback to old system if anything goes wrong. This will allow the post implementation
process with better quality. The development release of an application after each iteration is a
great way of controlling the deployment strategy. The parallel strategy will be supporting the
system deployment through providing various options to the project manager.
4. Security:
The authorization is the way of verifying whether the user have access to particular asset
of the system. Authorization can be the best of securing the access to the device. This will allow
the system to have users that are restricted to a very small amount of access, on the other hand
the admins will be provided with a high amount of authority over the system. The authentication
technique, on the other hand, is the process of restricting the access to the system. This will be
done through implementing a verification application within the system. The users will have
different unique id to login to the system. If the provided id matches with the one stored in
system, then only access to the device will be granted. Recognizing the MAC address of the
system and checking if any new device is used for connecting to the system is the way of
protecting the data being transmitted to the foreign devices.

7SYSTEMS DESIGN REPORT
5. Database Schema:
Figure 5: CHEMEXEC Organization Entity Relationship Diagram (ERD)
(Source: Created by Author)
6. Risk Management:
Potential Risk Likelihood Impact Countermeasure
Additional cost of Medium Medium Minimize

8SYSTEMS DESIGN REPORT
implementation
Not meeting the
predefined deadline of
project delivery
High High Minimize
Inadequate allocation
of resource through
Medium High Prevent
Less support from
stakeholder than
required
Medium High Minimize
Inappropriate
scheduling
Medium Medium Prevent
7. Reflection:
As a member of the group I was responsible for carrying out various activities to
complete the project within time and with quality. I have done the UML diagrams like, sequence
diagram and class diagram. As the class diagram and database schema needed to be matched as
per attribute standard, I have helped my team members to realize the attributes of the ERD or
Entity Relationship Diagram. The risk management part has been done by us all. Designing the
network diagram was a tricky task and I have design the basic layout of the network diagram,
upon which the whole diagram has been generated.

9SYSTEMS DESIGN REPORT
Bibliography:
Booth, C., Cheluvappa, R., Bellinson, Z., Maguire, D., Zimitat, C., Abraham, J. and Eri, R.,
2016. Empirical evaluation of a virtual laboratory approach to teach lactate dehydrogenase
enzyme kinetics. Annals of Medicine and Surgery, 8, pp.6-13.
Cabot, J., Clarisó, R. and Riera, D., 2014. On the verification of UML/OCL class diagrams using
constraint programming. Journal of Systems and Software, 93, pp.1-23.
Cagiltay, N.E., Tokdemir, G., Kilic, O. and Topalli, D., 2013. Performing and analyzing non-
formal inspections of entity relationship diagram (ERD). Journal of Systems and Software,
86(8), pp.2184-2195.
Dennis, A., Wixom, B.H. and Tegarden, D., 2015. Systems analysis and design: An object-
oriented approach with UML. John Wiley & Sons.
Hu, Y., Zhang, X., Ngai, E.W.T., Cai, R. and Liu, M., 2013. Software project risk analysis using
Bayesian networks with causality constraints. Decision Support Systems, 56, pp.439-449.
Jena, A.K., Swain, S.K. and Mohapatra, D.P., 2015. Test case creation from UML sequence
diagram: a soft computing approach. In Intelligent Computing, Communication and Devices (pp.
117-126). Springer, New Delhi.
Kumar, B. and Singh, K., 2015. Testing uml designs using class, sequence and activity diagrams.
International Journal for Innovative Research in Science and Technology, 2(3), pp.71-81.
Marcelino-Sadaba, S., Perez-Ezcurdia, A., Lazcano, A.M.E. and Villanueva, P., 2014. Project
risk management methodology for small firms. International Journal of Project Management,
32(2), pp.327-340.

10SYSTEMS DESIGN REPORT
Panthi, V. and Mohapatra, D.P., 2013. Automatic test case generation using sequence diagram.
In Proceedings of International Conference on Advances in Computing (pp. 277-284). Springer
India.
Rumpe, B., 2014. Executable Modeling with UML. A Vision or a Nightmare?. arXiv preprint
arXiv:1409.6597.
Vanetti, M., Binaghi, E., Ferrari, E., Carminati, B. and Carullo, M., 2013. A system to filter
unwanted messages from OSN user walls. IEEE Transactions on Knowledge and data
Engineering, 25(2), pp.285-297.