Mamma Mia Project Portfolio: User Requirements & Design Analysis

1 Project Portfolio. Your name Institutional affiliation Course Date

2 Contents 1. Planning and User Requirements ............................................................................................. 3 1.1. The company and the System’s Environment ................................................................... 3 1.2. Requirement Lists ............................................................................................................. 3 1.2.1. Home Page ................................................................................................................. 4 1.2.2. Layout Information .................................................................................................... 4 1.2.3. Navigation .................................................................................................................. 4 1.3. Economic Feasibility ......................................................................................................... 4 1.4. Structure of the project using SCRUM ............................................................................. 6 1.4.1. Structure of the project .............................................................................................. 6 1.4.2. Initialization of Activities .............................................................................................. 6 1.4.3. Proposed Mamma Mia intermediate deliverables ......................................................... 6 2. Phase 2 - Data Flow Analysis .................................................................................................. 7 2.1. DFD Diagrams .................................................................................................................. 7 2.1.1. Context Diagram Level 0 ........................................................................................... 7 2.1.2. Level 1, Requisition and Vendor Selection ................................................................ 8 2.1.3. R ................................................................................................................................. 9 3. Phase 3 - Entity-Relationship Model & Database Design ....................................................... 9 Reference ....................................................................................................................................... 10

3 1. Planning and User Requirements. 1.1. The company and the System’s Environment . Mamma Mia is a famous enterprise recognized for the production and distribution of dry pasta products to several outlets and supermarkets. The organization produces its commodity in its 20 plants. The organization is based in Denver, Colorado, where its operations are pioneered. To effectively manage its operations, the organization developed a comprehensive and modern home-made information system that lacks systems for purchasing and accounts payable. The present system uses a client-server-server architecture that runs on HP-UX servers and an Oracle database. 1.2. Requirement Lists. The fundamental requirement of this system is to facilitate the purchasing of products from the organization. This implies that the system must be able to process the purchasing request and forward it to the sales department. The request shall include the details of goods and services requested by a customer, their respective prices, and any special consideration. After the request has been sent, the sales department will approve the request based on the existing quantities of goods or any other constrictions. Organizational policies and procedures shall also be implemented in the system. This phase of assessment of the requirement is significant as it guarantees the possibility of resolving the existing problem. Implementation of these services over the web shall also be a step towards providing a sustainable solution. Implementing the system over the web will entail having the home page, layout structure, and navigation.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

4 1.2.1. Home Page. The home page is the landing page for every user and will contain important information such as product information, announcement banner, log-in or create account options, shopping cart, and important organizational information such as contact. 1.2.2. Layout Information . The layout describes the structure of the website. One of the website layout structures is the navigation menu. The navigation menu should be designed to appear on every webpage to make it easy for customers to navigate across the system. The other aspects of the layout are the graphical interface. A graphical interface should be designed with consideration of simplicity, and relatability to actual functionalities. When designing the graphical interface, the load time of the site should also be a major consideration. 1.2.3. Navigation. Navigation should be made simple to make the process of purchasing and checking out friendly to the user. The purchase menu/checkout menu should be universally available on all pages for customers to access from any page of the website. The option to view whatever has been selected to the shopping cart should also be available. For the organization to reduce operations time, the best-selling products or the most searched products should be automatically loaded to the home page menu. 1.3. Economic Feasibility. Before implementation of any financial project, an analyst must ensure that it guarantees financial equity (value for money). Taking an example of a similar organization, the implementation of such a system on Mamma Mia could guarantee the benefits of up to $185,00

5 annually. The initial cost of the system (one-time cost) is approximately $275,000 and an associated recurrent cost of management of $85,000 should also be factored in. Given the nature of the system, it is designed to give a discount of 12% of the benefits accrued. Taking the timeline of five years after its initial implementation, the table below presents the anticipated value provided by the system cumulatively for the period. Based on the above analysis, the acquisition of the purchasing information system is projected to improve critical operations in Mamma Mia by reducing the technicalities in logistics and supply chain by ensuring that there is a smooth purchasing procedure. Apart from the economics of the system, the system will eradicate the challenges encountered in purchasing by automating most processes which will in the long run guarantee a quality customer experience. The system shall also guarantee timely communications between the various departments within the organization i.e. sales department, logistics, and vendors.

6 1.4. Structure of the project using SCRUM. 1.4.1. Structure of the project. This project will utilize the programmatic structure. This is an ancient technique where managers have formal authority over most of the organizational resources. This technique is highly effective considering that the system being developed is for one section of the organization (purchasing). This process shall be undertaken in the purchasing department only and all the resources such as staff required for the project will only be sourced from the department. 1.4.2. Initialization of Activities. Part of the initializing activities entails the creation of a list of vendors. This list will constitute several suppliers who will supply the products to the organization. The other structural initialization activity includes the development of the purchase order which will constitute the information regarding the purchasing activities of the enterprise. Lastly, it will also be important to consider developing delivery and receiving notes which will be issued to the vendor upon delivery and acceptance of products. 1.4.3. Proposed Mamma Mia intermediate deliverables. The first deliverable of the proposed SCRUM is the sprint plan meeting. This meeting will unveil the tasks that are to be executed. Mamma Mia’s management team will also have an opportunity to meet with the project team members and deliberate on specific aspects of the product’s backlog. The other deliverable is the daily scrum which constitutes daily interactions by members where they will discuss meetings of the previous days, and the activities to be executed in the

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

7 day. These meetings will be short but will help the sprint team to agree on various project aspects. Sprint reviews will be done upon the conclusion of a specific sprint and it will entail seeking feedback from Mamma Mia's management and other players in the department. Lastly, a sprint retrospective shall be conducted at the end of all the sprints of retrospective meetings. This will enable the team members to reflect upon and identify any opportunities for improvement of the system (Valacich & George, 2017). 2. Phase 2 - Data Flow Analysis. 2.1. DFD Diagrams. 2.1.1. Context Diagram Level 0.

8 The above level one diagram above is a representation of the source systems that contribute data to the system. The diagram helps in the definition of software boundaries and identifies the flow of information between the system and external bodies (Ronen-Harel, 2014). The diagram highlights various entities that interact with the system, such as the warehousing department, vendors, the receiving department, and the requisitioning department. 2.1.2. Level 1, Requisition and Vendor Selection. The level one diagram below indicates the flow of data from the requisition to the identification and selection of vendors. Level one diagram is an annotation of the sub-processes that can easily be analyzed and enhanced. The diagram above shows that after the requisition need has been advanced, the purchase requisition is prepared and sent to the purchasing

9 department. The purchasing system uses policies and procedures to determine whether the purchasing requisition should be rejected or accepted. The DFD is easy to comprehend and simple to follow compared to the context diagram. Level 1: Purchasing and warehousing. The diagram above constitutes for purchasing to warehousing of goods. The major process entails acceptance of purchase requisition, order processing, and the inspection of commodities. After the acceptance has been made, an order for purchase is created, and copies are sent to the payable, receiving department, and a vendor who facilitates formal communication from the organization upon completion of the purchase.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

10 3. Phase 3 - Entity-Relationship Model & Database Design. 3.1. Design. An ERD diagram is used to show the association between entities constituted in an enterprise (Valacich & George, 2017). The entities are defined and modeled based on the needs of the enterprise. Physical or Logical ERD can be utilized. Logical ERD For Mamma Mia. The above ERD indicates the first entity as the order requisition dimension. The logical ERD above shows different categories of data attributed to the entities, including the name of the

11 order and the description of the requisition. The order requisition is associated with the purchase order entity since the purchase order is made utilizing requisition. Physical ERD. Physical ERD is used to physically describe the actual structure of the database. Physical ERD converts the database design to a schema-level design that can be translated into a rational database. Couture describes that in the conversion of logical ERD to physical ERD, the logical ERD acts as the base with several refinements and defines primary keys, foreign keys, and constraints (Couture, 2015).

12 The physical DFD better describes the database since it elaborates on foreign and primary keys for the order purchased. For instance, the primary key for the order requisition is requisition ID, this key acts as a unique identifier for each requisition made. Order ID is different and therefore becomes a distinct identifier in the database. Also, the vendor number is unique in some way and becomes a foreign key in the product dimension. 4. Phase 4 – Implementation. 4.1. Test Plan. Testing is an essential part of the project after it has been developed, this ensures that the project achieves the development requirements. According to Bass and Zhu, a test plan strategy documents the techniques that are to be used in the examination and verification of the final product concerning the anticipated outcomes and the requirement specification (Bass & Zhu, 2015). Part of the tests to be undertaken include end-user acceptance testing, performance testing, and security testing. An analysis of the performance is also essential to ensure that the project meets the expected performance requirements. Performance testing is the most significant test that must be carried out in the Mamma Mia purchasing system project. Since the project was implemented to facilitate purchasing, the system should offer an effective flow of information between the different entities within the system right from the requisitioning department, vendors, accounts payable, and warehousing (Waller, 2015). Other tests to be carried out include workforce acceptance, skills possessed by the workforce, the effectiveness of the product (system), and compatibility with other organizational systems for integration.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

13 4.2. Training Plan. After the project has been tested, the next step entails ensuring that there is competent personnel that can optimize the capabilities of the system. All staff including the non-technical members are eligible to undergo the training. The training will address the need for requisite skills for the system and executing various commands in vendor selection, rejection and approval of orders, and communication between various system entities (Rahman & Williams, 2016). The training will also constitute system operations and processes. The training will be comprehensive and will be executed for a considerably long time. The organization will distribute training manuals to every employee. The manual will contain a description of the system and the operations in each section of the system. This program expects that the staff will be able to work with the system with a proper understanding of the operations by the end of the training session. 4.3. DevOps. Waller describes DevOps as the changes in the organization's Information Technology Culture with the rapid transitions to implementation of information technology in every aspect of the organization (Waller, 2015). The process seeks to promote collaboration between the organizational operations and the system development team. Why does Mamma Mia need DevOps? The enterprise will need to institute DevOps for effective system performance because ensures that rollbacks, failures, and recovery times are limited (Manivong, 2018). The process exposes code defects and releases required codes hence reducing the time required to develop the system. DevOps also improves collaboration and communication to enhance system development. DevOps teams have developed a culture of trust and ensuring that performance is

14 emphasized rather than a member’s goals. The process will also promote innovations, reduce the development cycle, and upgrade. Costs. DevOps will ensure that the enterprises maximize the value for money for performance and quality. However, it comes at a cost. Part of the costs includes adoption costs. This includes the training of team members, testers, developers, and end users. Other costs include capital costs and additional staffing. Financial Implications. The financial benefit of the adoption of DevOps includes a reduction in costs. Yearwood describes that DevOps teams are likely to reduce costs by up to 35% and the need for additional staff by 30% (Yearwood, 2016). Faster upgrades and innovations including shortened development cycles will also guarantee reduced financial responsibilities. Collaboration and communication facilitate quicker resolutions and eliminate system failures. Other benefits. Mamma Mia will benefit from reliability. Code changes will be developed, tested, and released through DevOps. Jabbari states that DevOps ensures that the system is being continuously monitored, limiting the chances of code defects and system failures (Jabbari, 2016). The Use of DevOps will also facilitate the automation of processes, which will help to reduce the amount of manual work and improve efficiencies.

15 4.4. DevOps Implementation Plan and Strategy. The first step is introducing the system to users of the system. The next step constitutes the development of the Deva strategy, which entails creating a collaborating team and devising new ways of provisioning infrastructure, and making individual and team goals known to everyone. The next step entails automation and QA-Deve alignment. The final step entails an implementation strategy that will be continuously evaluated and monitored to ensure that it meets the performance expectations.

Your preview ends here

Eager to read complete document? Join bartleby learn and gain access to the full version

Access to all documents
Unlimited textbook solutions
24/7 expert homework help

16 Reference. Bass, L., & Zhu, L. (2015). DevOps: A software architect's perspective. Addison-Wesley Professional. Couture, N. (2015). Building the foundation with a high-level architecture. Retrieved from https://www.cio.com/article/3003890/data-warehousing/building-the-foundation-with- ahigh-level-architecture.html Jabbari, R. (2016, May). What is DevOps? A systematic mapping study on definitions and practices. In Proceedings of the Scientific Workshop Proceedings of XP2016 (pp. 1-11). Manivong, K. (2018). Towards a smart project management information system. International journal of project management, 16(4), 249-265. Rahman, A. A. U. & Williams, L. (2016, May). Software security in DevOps: Synthesizing practitioners' perceptions and practices. In the 2016 IEEE/ACM International Workshop on Continuous Software Evolution and Delivery ( CSED) (pp. 70-76). IEEE. Valacich, J. S., & George, J. F. (2017). Modern systems analysis and design (8th ed.). New York, NY: Pearson. Waller, J. (2015). Including performance benchmarks into continuous integration to enable DevOps. ACM SIGSOFT Software Engineering Notes , 40(2), 1-4. Yarwood, D. L. (2016). U.S. Patent No. 5,563,998. Washington, DC: U.S. Patent and Trademark Office

Portfolio Project.edited

Related Documents