Stage 3: System Design Specification Before you begin this assignment, be sure you have read the Case Study and all assignments for this class, especially Stage 4: Final System Report. The feedback you received on your Stage 1 and Stage 2 assignments should be reviewed and used as you proceed with Stage 3. Purpose of this Assignment This assignment gives you the opportunity to apply a systematic approach to translate requirements into a high-level logical system design. This assignment specifically addresses the following course outcomes to enable you to: • • apply a systematic approach to translate requirements into an executable systems design effectively communicate with stakeholders to determine, manage, and document business requirements throughout the SDLC Assignment The results of your systems analysis and design work in this class will be documented in a Final System Report. The purpose of the Report is to inform management of your system proposal and gain approval to proceed with the project. The Report will be developed and submitted in stages, which will be compiled at the end of class into the Final System Report. Review the outline of the Final System Report in the Stage 4 Assignment description. Note that it contains the analysis of the problem(s) and requirements, and proposes what kind of a system solution is needed. It does not propose a specific solution, but it does recommend why and how the organization should acquire the solution. Following the Requirements Specification (Stage 2 assignment), the next step is to develop the System Design Specification. The System Design Specification builds on the Requirements Specification to illustrate how the files/database(s) will be laid out, how the output (forms, reports, and/or screens) and input (forms and/or screens) should be designed. As you develop this assignment, you should refer to your Stage 2 Requirements Specification (and the feedback you received) and use the inputs and outputs you listed to create the input and output layouts and the file/database design. All of the information you need to complete the projects in this class is not provided in the case study. In the discussion area of the classroom, there is a discussion titled "Case Study Interview Questions" where you can pose questions about the case study, as if you were interviewing the people in the case study organization. Any information that you need that is not included in the case study should be asked about in this discussion. Responses from the faculty member on behalf of the case study organization will be available for everyone in the class. Use the case study and the Case Study Interview Questions discussion, along with your Stage 2 Requirements Specification (including the feedback received), and resources below, to create a System Design Specification in the format shown below. Include your corrected Stage 2 Requirements Specifications as the first part of this assignment. Approximate lengths for each section of the Systems Design Specification are provided as a guideline; be sure to provide all pertinent information. The sources of explanatory materials can be found in the Week 5 Content readings. Stage 3: System Design Specification 1 Requirements Specification Include your Requirements Specification from Stage 2, with corrections from the feedback included. This will establish the context for your System Design Specification to follow. System Design Specification I. II. III. IV. Introduction. Provide an appropriate introduction to this document. (one paragraph) Output Layout. Begin with the three outputs listed in your Requirements Specification. For each of them, create a diagram or table illustrating what the output would look like. (use a short paragraph to introduce this section and each diagram, table or illustration should use about ½ of a page) A. Output Layout #1. B. Output Layout #2. C. Output Layout #3. Input Layout. Using the data elements listed in your Requirements Specification, create a diagram or table illustrating what the input screen would look like for each of the three sets of input. (use a short paragraph to introduce this section and each diagram, table or illustration should use about ½ of a page) A. Input Layout #1. B. Input Layout #2. C. Input Layout #3. File/database Design ERDs. For each of the three sets of outputs and inputs, create an Entity Relationship Diagram showing how the data elements are related to each other [see explanation at http://academic.regis.edu/ladams/Diagramming%20101.html]. Depending on the inputs and outputs identified, there may be some overlap of the data elements in the ERDs; a separate ERD should be developed for each pair of inputs/outputs. (use a short paragraph to introduce this section, and each ERD should be on one page) A. File/database Design ERD #1. B. File/database Design ERD #2. C. File/database Design ERD #3. Submitting Your Assignment Submit your Requirements Specification and System Design Specification as one document via your Assignment Folder as Microsoft Word document, or a document that can be ready using MS Word, with your last name included in the filename. Use the Grading Rubric below to be sure you have covered all aspects of the assignment. GRADING RUBRIC: Stage 3: System Design Specification 2 Criteria Introduction Output Layouts Input Layouts File/Database Design ERDs 90-100% 80-89% 70-79% 60-69% < 60% Far Above Standards Above Standards Meets Standards Below Standards Well Below Standards 5 Points 4 Points 3.5 Points 3 Points 0-2 Points The corrected Requirements Specification is included along with a well-written introduction to the Systems Design Specification; demonstrates a sophisticated level of writing. The corrected Requirements Specification is included along with an appropriate introduction to the Systems Design Specification; demonstrates clear writing. The corrected Requirements Specification is included along with an introduction to the Systems Design Specification. The corrected Requirements Specification and/or the introduction to the Systems Design Specification may not be included or may not be complete. The corrected Requirements Specification and introduction to the Systems Design Specification are not included, or little effort is demonstrated. 27-30 Points 24-26 Points 21-23 Points 18-20 Points 0-17 Points 30 Three output layouts are clearly and logically presented; and very clearly relate to the output requirements previously defined. Demonstrate a sophisticated level of analysis. 27-30 Points Three output layouts are clearly presented; and clearly relate to the output requirements previously defined. Demonstrate accurate analysis. Three output layouts are presented and relate to output requirements previously defined. Fewer than three output layouts may be provided, and/or they may not be appropriate to the previously defined output requirements. 24-26 Points 21-23 Points One or no output layouts are provided, may not relate to the previously defined output requirements, or little effort is demonstrated. 0-17 Points 30 Three input layouts are clearly and logically presented; and very clearly relate to the input requirements previously defined. Demonstrate a sophisticated level of analysis. Three input layouts are clearly presented; and clearly relate to the input requirements previously defined. Demonstrate accurate analysis. Three input layouts are presented and relate to input requirements previously defined. 27-30 Points 24-26 Points 21-23 Points 18-20 Points One or no input layouts are provided, may not relate to the previously defined input requirements, or little effort is demonstrated. 0-17 Points 30 Three Entity Relationship Diagrams may not be included, Fewer than three Entity Relationship Diagrams are Three Entity Relationship Diagrams are correctly Three Entity Relationship Diagrams are correctly Stage 3: System Design Specification Three Entity Relationship Diagrams are adequately 18-20 Points Fewer than three input layouts may be provided, and/or they may not be appropriate to the previously defined input requirements. Possible Points 5 3 Format constructed, logical, appropriate to the inputs/outputs, and demonstrate a sophisticated level of analysis. 5 Points constructed, logical, appropriate to the inputs/outputs, and demonstrate accurate analysis. constructed, and appropriate to the inputs/outputs. and/or may not be appropriate to the inputs/outputs. 4 Points 3.5 Points 3 Points Submission reflects effective organization and sophisticated writing; follows instructions provided; uses correct structure, grammar, and spelling; presented in a professional format; any references used are appropriately incorporated and cited using APA style. Submission reflects effective organization and clear writing; follows instructions provided; uses correct structure, grammar, and spelling; presented in a professional format; any references used are appropriately incorporated and cited using APA style. Submission is adequate, is somewhat organized, follows instructions provided; contains minimal grammar and/or spelling errors; and follows APA style for any references and citations. Submission is not well organized, and/or does not follow instructions provided; and/or contains grammar and/or spelling errors; and/or does not follow APA style for any references and citations. May demonstrate inadequate level of writing. not provided, are not appropriate to the inputs/ outputs or little effort is demonstrated. 0-2 Points Document is extremely poorly written and does not convey the information. TOTAL Points Possible Stage 3: System Design Specification 5 100 4 1 Feasibility Study of a Project Loic Djamen 1/21/2018 Preliminary Investigation Report 2 Feasibility Study Of A Project Introduction The CIO, CFO and the VP of the telecommunication SME have the role of working as a team in a bid to deliver a feasible system for the company. Since the company has been in existence for about a decade, the involvement of an IT system specialist must produce the best course of action in the provision of an IT system that caters for the needs of the business both electronically and the billing system with regards to payment orders and accounts receivables. The following analysis undertakes to cover the benefits of a new system in a small entity, the feasibility study involved in its implementation and eventually the recommendations by the IT System analysts on the way forward in lining up the system data with all departments in the organization. Problem getting solved The background of the investigation and the project getting undertaken takes us back to the backlog experienced in the billing and payment processes. It has come to the analysts’ attention that all systems have majorly expanded with shipping and orders increasingly bulging. For the same reason, the operations in IT, finance and administration have significantly slowed necessitating the installation of a new system that would operate efficiently and efficiently. Lastly, the above identification means that all departments need to get overhauled by improving the Operating systems and making it easy to access and come up with better procedures for the business (Laird, 2008). Scope of the proposed system 3 It would become prudent to involve a system expert in the overhaul of the company information. The company has grown and is currently facing changed dynamics. Therefore, the presence of experienced specialists would go in a long way to identify the boundaries that the system would come. Since the whole system has its goals rotating around payment and the billing services experience, the people involved would undoubtedly surround the finance and accounts payable persons. Others may get involved for support purposes but not necessarily for the execution of the whole electronic system. The electronic system starts from the shipping, ordering and all the way to the payment methods that comes at the output of the entire material matter involved. The scope of the whole phenomena leads the research to the fact that everybody ensures automatic adjustments and improvements across the entire segment and the analogies meant. Constraints Constraints refer to the challenges that the IT people face in the management and the implementation of the new project. The restrictions here points to the budgetary allocation of the project and the program. The company deems it impossible to incur the costs of the assignment and the implementation of the whole concept of electronic and payment processes that are modern for that allocative year (Recker, 2010). Fact-finding The sales and the shipping orders get reported on a monthly basis for the reasons of getting the coding and the networking processes. The new system seeks to make quotations and shipments tied together to provide the best choice with regards to the performance and the development of monthly reports. Additionally, the system has various profiles including the 4 names of the customers, their addresses and the selling price for the services rendered. However, the system lacks the electronic payment field, the quantity discount allocation approaches, and the payment calculation options. With the installation of the system, the organization stands a better chance of dealing with the inequities of poor payment processes and also the problems o system analysis and calculations on prices. Current cost of the system The operational scope of an It system requires the input of the organization and other departments involved in the whole phenomena. Many companies install interfaces that go in line with their strategic goals and objectives with regards to their financial needs. Of importance is to narrow down to the estimated costs of operating an accounting system for example. The QuickBooks, for instance, would serve the organization far and wide. Therefore, the values here would become and revolve around 900 – 20000 USD. Per annum. Depending on the size of the group, QuickBooks costs vary, and since the one under study is a medium organization, an estimated operational value of about 6000 USD becomes entirely on point. Feasibility studies of the project The feasibility study in any proposal goes a long way to come up with the best courses of action with regards to the allocation and project design and viability. A plan may get seen as either technically or financially viable depending on the surveillance conducted on the same during a particular stretch of time on implementing its deliverables. Technical feasibility The question here for any manager is doing the company have the prerequisite capacity to handle the change. The environmental feasibility study promotes the viability of a project by 5 coming up with alternative sources and courses of action by employing the correct and specialized workforce in the allocation and upgrade of the interminglement reporting system. Financial feasibility The sector here brings about exciting aspects of the company. It goes on to evaluate the cost-benefit analysis of the whole project. The company should come and conclude together with the IT steering committee that the benefits of implementing the system would by far outweigh the costs implications. It does so by improving efficient delivery of services and also the provision of all technological allocations that come with the whole activities (Finnerty, 2013). Behavioral feasibility The IT steering committee has to study group dynamics and commitment to delivering the goods and services for its clientele. First and foremost, positive behavioral attributes would promote the public image of the company by enshrining trust in the whole process for the god of its implementation. Since people required for the same, belief forms a big part of the entire phenomena and must get included in the decision-making parameters. Recommendations for the entire action Since most project segments have an estimated period of six months to come up with the best and the new procedural allocations, many organizations find it hard to produce the best management allocations and recommendations on the same. On the contrary, the case herein points to the fact that the people involved are hell-bent on providing the best out of the combined periods. In connecting the three areas under investigation, the whole activity would take about two years to complete both the sales, accounts receivables, administration and operative segments 6 Tangible and intangible benefits on its implementation The business stands to benefit immensely from the application of the above issues. It becomes reasonable to state that a comprehensive and timely report would get generated on a daily basis and thus make the company a good and a progressive place of doing business at any given time in the discharge of duty. The other benefits we can see go to the infrastructural adjustments. The company would become in a position to develop and earn its rightful place thus increase capacity building and draw on its line of competency allocations (Sumanjeet, 2009). 7 References Finnerty, J. D. (2013). Project financing: Asset-based financial engineering. John Wiley & Sons. Laird, D. A. (2008). The Charcoal Vision: A Win–Win–Win Scenario for Simultaneously Producing Bioenergy, Permanently Sequestering Carbon, while Improving Soil and Water Quality All rights reserved. No part of this periodical may be reproduced or transmitted in any form or by any means, electronic or mechanical, including photocopying, recording, or any information storage and retrieval system, without permission in writing from the publisher. Agronomy journal, 100(1), 178-181. Recker, J. (2010). Opportunities and constraints: the current struggle with BPMN. Business Process Management Journal, 16(1), 181-201. Sumanjeet, S. (2009). Emergence of payment systems in the age of electronic commerce: The state of art. 1 System Requirement Project Loic Djamen IFSM 461 February 4, 2018 SYSTEM REQUIREMENT PROJECT 2 System Requirement Project Introduction Different projects come with changing dynamics in the implementation of output, input, and processing. The systems analysts just as in project one have the primary function of coming up with improved information technology operational distinct thus efficient and effective financial, technical and behavioral tendencies/requirements. The project at hand looks at establishing a public cafeteria blog. The blog should contain a platform that can communicate cafeteria news, events, resources and eventually provide users with an ability to respond to the comments on the website. The following analysis seeks to come up with functional, technical and the scoping study for the cafeteria project and give diagrammatic representations of the same for the implementation of a proper and improved cafeteria IT functions. Functional requirements The use of blog-posts makes the functionality of the whole activity proper. When looking at the implementation of the project, the paper seeks to identify three input needs plus other three output needs. Different levels of the organization would need to make a decision on the best input model based on a feasibility report carried out. The service need for the project refers to the need of communicating adjustments to the blogs on policies, procedures and many activities at any particular juncture. The next question goes-what are the three needed input requirements for the organization? Input requirements There are three input objectives that the cafeteria would require to execute its mandate properly. Additionally, the elements needed for improving the three input circles would go in a SYSTEM REQUIREMENT PROJECT 3 long way to come up with the best chance scenario of marketing the techniques suggested. Users can receive individual emails that contain blog contents. The element in the above-stated need and input refers to the Gmail account formation. The sender and the recipient of the emails need such an account. The use of the element above improves all matters in the whole activity. The next input requirement refers to the forwarding of date posts. Forwarding posts in any blog require the aspect of server management. Servers and webs must have such features that allow forwarding of the emails at hand. The last input points to the users creating profiles. An example of such an element leads to the gravatars. The gravatars gives such features that allow brewing and editing the content of the whole matter. Undoubtedly, the organization has the role of ensuring the primary responsibility of developing policies and procedures in processing the entire configured issues establishes activity as the whole (Karras, et al 2017). Output requirement The output criteria for the above issue point to the very needs of the cafeteria. First and foremost, users have the liberty to comment on the blog posts. The site provides users with the very lack of producing a platform for coming up with the prepared comments. The site has the SDL avenue for feedbacks whereby the users have the liberty to comment and or come up with technical needs for the open matter. The next output in the descriptions here points to the fact that the administrators can edit, rewrite and lastly produce the roll-up posts for the provided information. Most importantly, the element of narrating and writing the website points to the C+++ program that makes the whole matter adjustable and produced for the good of the company. Lastly, the users can subscribe to the blog posts needs and make it possible to develop an RSS that enables the organization implements the variable technological accuracies for the provided period. SYSTEM REQUIREMENT PROJECT Processing requirements The process of coming up with the available processing objectives heavily relies upon output one, two and three in the discussion channels. The need for the user to comment on the blog post would necessitate a browser processing line. Yes, a browser is needed to put in place the contents of the research and the cafeteria resources and citations for the good of the organization and the implementation of the technical management appraisal authority. Next, we have the alternative approach models. Save for the c+++ models; there are a couple of programs such as Java that need to exist for the processing of the cafeteria policies that get pinned on the website for the good of the entity. Eventually, the management has to ensure that the processing approach implemented that can enable subscription refers to the mobile user sensitive approach and strategy (Backes, et al 2015). Technical requirements When the research area talks about the technical feasibility, we have a plethora activity bombarding a system analysts mind. First and foremost, the analysts would have to look at the human resources that get used in the execution of the whole plan. The human resources bridge the gap between technical feasibility and financial feasibility thus system requirement get handled. The following areas need close evaluation in analyzing technical requirements of a cafeteria blog and their explanations Security requirements The security needs of the cafeteria blogs are unmatched. They must get top notch and consistent with the available information technology goals of a particular organization. The notable feature in the security appliances used herein points to the use of passwords and log in 4 SYSTEM REQUIREMENT PROJECT 5 cards. The server would get secure when the above get implemented. Next issue refers to the cafeteria management appointing a competent network administrator who gets responsible for manning security on a twenty-four-hour basis to guard against unauthorized users. Lastly, the use of the firewalls would enhance security features for the cafeteria resources. The cafeteria needs secure and sound firewalls to handle its operations and documentation protection. System control requirements In the data management field, we have two types of controls-the logical controls and the system controls. The logical controls need applications by the person in charge. For example, in our case, we require the use of biodata identification strategies. The authorized personnel has to come up with convincing reasons to promote the functional and the integrity of the firm. Next, the application of the whole backup maintenance approaches makes it easy to control against external attacks. Lastly, the company has to devise strategies to ensure only authorized people to make entry and can erase the information in the blogs. Performance requirements The system has the primary goal of ensuring users can access whatever needed at any time for use. The system is required to deliver and perform the output functions aforementioned. Number one, the application and the add created makes it very articulate to come up with the best technology to develop likable policies among the available cafeteria workers. The other requirement here points to the fact that the subscription goal satisfies the financial condition of the thus navigate the murky waters at hand. Most importantly, the organization must intertwine the control, systems security and the available processing requirements (Combes et al 2015). Business continuity requirement SYSTEM REQUIREMENT PROJECT 6 The system analysts have no choice but to proceed right to the three-step requirement process. At number one there exists the backup goal. The company must have up to date backup models for use in the facility to allow dosv=ctors, professors and students easily trace their work for the good of the whole system. Next, there comes the recovery stages and lastly, the restart feature of the company. Web scope diagram It's essential to locate the environment in which the software applied operates and rotates. The figure below indicates a hypothetical diagram for the cafeteria electronic ordering system that comes with a series of facts. The circle tells of a system boundary. The same, and the interrelationship between external also represent the name of the method and internal online allocations are mentioned and pointed by the arrows. Use case diagram The case diagram just as the context diagram has representations about the internal forces interacting with the external forces. The circle tells of a system boundary. The same and the interrelationship between external also represent the name of the system and internal online allocations are mentioned and pointed by the arrows. See the diagram below. SYSTEM REQUIREMENT PROJECT Use case diagram 7 SYSTEM REQUIREMENT PROJECT 8 Data diagram/flow diagram Data entry in the blogs such as viewing input information Expanding the files for other activities and alternatives Updating the menu and organizing edited pages Examining the blogs for errors and securing cafeteria files SYSTEM REQUIREMENT PROJECT 9 Process models The process models here would examine three crucial parts of the project. First and foremost, there is the input model. We have the process model, and lastly, we have the output model. The following diagrams give a preview on how to handle the whole matter (Braglia., & Frosolini 2015). INPUT HOTEL ORDERING SYSTEM OUTPUT PROCESSING SYSTEM REQUIREMENT PROJECT 10 References Braglia, M., & Frosolini, M. (2014). An integrated approach to implement project management information systems within the extended enterprise. International Journal of Project Management, 32(1), 18-29. Combes, J., Kerckhoff, J., & Sarovar, M. (2017). The SLH framework for modeling quantum input-output networks. Advances in Physics: X, 2(3), 784-888. J., Cofer, D., Miller, S., & Whalen, M. W. (2015, April). Requirements analysis of a quadredundant flight control system. In NASA Formal Methods Symposium (pp. 82-96). Springer, Cham. Karras, O., Klünder, J., & Schneider, K. (2017). Indicating Potential Risks for Project Success Based on Requirements Fulfillment. Softwaretechnik-Trends: Vol. 37, No. 2.
Purchase answer to see full attachment