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: Criteria 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 Introduction Possibl e Points 5 Stage 3: System Design Specification 2 The corrected Requirements Specification is included along with a wellwritten introduction to the Systems Design Specification; demonstrates a sophisticated level of writing. Output Layouts 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 Requirement s Specification and introduction to the Systems Design Specification are not included, or little effort is demonstrate d. 30 27-30 Points Three output layouts are clearly and logically presented; and very clearly relate to the output requirements previously defined. Demonstrate a sophisticated level of analysis. 24-26 Points 21-23 Points 18-20 Points 0-17 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. One or no output layouts are provided, may not relate to the previously defined output requirement s, or little effort is demonstrate d. Stage 3: System Design Specification 3 Input Layouts 30 27-30 Points Three input layouts are clearly and logically presented; and very clearly relate to the input requirements previously defined. Demonstrate a sophisticated level of analysis. File/Databa se Design ERDs 24-26 Points Three input layouts are clearly presented; and clearly relate to the input requirements previously defined. Demonstrate accurate analysis. 21-23 Points Three input layouts are presented and relate to input requirements previously defined. 18-20 Points 0-17 Points Fewer than three input layouts may be provided, and/or they may not be appropriate to the previously defined input requirements. One or no input layouts are provided, may not relate to the previously defined input requirement s, or little effort is demonstrate d. 18-20 Points 0-17 Points Three Entity Relationship Diagrams may not be included, and/or may not be appropriate to the inputs/outputs. Fewer than three Entity Relationship Diagrams are not provided, are not appropriate to the inputs/ outputs or little effort is demonstrate d. 30 27-30 Points 24-26 Points 21-23 Points Three Entity Relationship Diagrams are correctly constructed, logical, appropriate to the inputs/outputs, and demonstrate a sophisticated level of analysis. Three Entity Relationship Diagrams are correctly constructed, logical, appropriate to the inputs/outputs, and demonstrate accurate analysis. Three Entity Relationship Diagrams are adequately constructed, and appropriate to the inputs/outputs. Format 5 5 Points 4 Points 3.5 Points 3 Points 0-2 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 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 Submission is adequate, is somewhat organized, follows instructions provided; contai ns 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 Document is extremely poorly written and does not convey the information. Stage 3: System Design Specification 4 cited using APA style. cited using APA style. demonstrate inadequate level of writing. TOTAL Points Possible Stage 3: System Design Specification 100 5 Udit Sehgal STAGE 2 Based on different problems that are based with precisions electronics parts it is clear that the main expectations of the developed model will focus on developing information technology system that will be critical in ensuring that small businesses related to the operations of the company are able to achieve their goals and strategies. It is also clear that the developed model is to basically replace the old computer system that has been an impediment to facilitates efficient operations in both the business administration and finance operations. It is also clear that the other focus that is entailed in developing a new system focuses on the developing a new invoice system that should facilitate new measures that would basically ensure smooth running of the PEP company. It is also clear that through adjusting the current billing system the company will have greater potential in accumulating financial staff which will not accumulate massive billing and payment system process. In the context of the above analysed requirements it is clear that the main focuses based on the above outlined problems will includes mitigating issues such as; In the context of developing new information system that is vital in ensuring efficient operations of small businesses related to the operations of the PEP Company. This is where the developed system should be able to ensure that a clear method of ordering and shipping and shipping commodities such as medical equipments to various regions of the sales is achieved considering the current demand based on delivering custom low voltage motors that has been related to more environmentally friendly. Udit Sehgal The company also evidently will achieve and create a well comprehensive system that would basically address the needs of various customers. This is where the information system should be able to ensure new customer relations through ensuring address of customers' complaints through minimization of the operating costs. The other focus that has been critical in ensuring that an efficient operation by the PEP Company is achieved is the improvement and replacement of the old computer is that the goal of addressing achieving financial administration. This is where the system should be able to address corrupt means is achieved through ensuring solving all financial credible means that are not easily manipulated. It is also clear that in the context of addressing the billing system the company will be able to ensure easier setting of the new salaries and pay structures are clearly addressed thus achieving a credible and transparent process. It is also clear that the company will be able to achieve easier facilitation process that is credible in setting new prices for various commodities that the company is deals and focus with. This then being the case in the long run the company will be able to achieve and ease their operations through ensuring adaptation of a more comprehensive model. Finally, the new billing system will be crucial in the context of ensuring that a clear update and transition in the sales department is facilitated. This then being the case, it is clear that the company sales department will be able to achieve better management standards thus upraising their productivity. Udit Sehgal In these scope then it is clear that each and every system will require various input to ensure the projected results are achieved for the case of the information system it is clear that main details that would vial based on small firms includes; The name of the firm, firms address, city where the firm is set, operational contact of firm, product order, order number quantity of the order, date of delivery of the order, calculated price and date the order was paid. The diagrammatic flow diagram based on this IT information should be clearly outlined as follows; Company name location and contact Specify the quality of the products to be deliivered. product order Quantity of order Date of order IT documentation Amount to be paid Date of delivery Signing of the order receive Invoincing paymenPERt of the invoice Conformation of invoice receivalbe by PEP company. In the above structure it is clear that the IT system will technically address locate the order made by different firms that the company deals and focuses in their operations this is where the order should be followed until the final delivery by the company is achieved. Udit Sehgal After the achievement of the delivery the PEP Company will be responsible in generating the invoice that the company will pay based on the number of products and the quality of the products that are to be delivered. After PEP company has developed the invoice which is agreed by the company where products are to be delivered then PEP company delivers the products where the order is receive by their customers indicating date of order,quantity,quality and the overall cost entitled in the entire process. This is where then the invoice is then paid regarding to PEPs requirement by the company using various means of payment. In this regards it is clear that the process is not complex thus each and every international firm is able to understand thus mitigating delays in delivery and achieving the quality offering of customers service which is the main shift by the company. In the context of the readjusting the billing technology that has been used within the operations of the PEP Company to hyper inflates the cost of operations thus leading to corruption. This then being the case he main data that should be entailed in the system should include and meet the goals of the company which is basically to reduce misuse of funds through corruption. For the case of checking on salaries payment The main input thus should entail name of employee, category of employee (casual or management), identification number, and salary scale, date of payment, amount paid and signature of the employee. The proposed system should entail a model that should structurally include; Udit Sehgal name of the employee category of the employee Identification number casual management salary payment date of payment salary payment date of payment signature signature system update The main goals of the company of the company are achieved through ensuring that the system is credible and does not propel corruption which has been an impediment. This then being the case, the company is able to delegate its operations with credibility and in generating returns based on the fact that the system will show any financial and procured by the company identified by the signature and identification card number. Through signature and conformation of the payment where the data is the automatically updated to the system it is clear that security is achieved since no repetitive corruption will be experienced in the company operations. In the context of the ensuring effective billing it is clear that the company has great role and responsibility in ensuring old computer system is enhanced in the context of ensuring bills backlogs are simplified entails the system including; The new computer system should focus on details such as; Udit Sehgal Serial invoice number, customer organization name, customer address and city, amount paid, amount paid and outstanding amount. lq r c v b iD d a s t n u o m g I y p f e A Through this developed model it is clear that the company operations will be able to infuse new measures such as identifying each customer using a unique identity number thus nullifying any backlogs based on customers invoicing which has been a clear issue. Udit Sehgal The security based on this system is that the system will be more secure due to use of the unique serial number and the ID number thus nullifying any double contract that is an impediment to effective operations. REFERENCES http://www.jamasoftware.com/blog/defining-project-scope-context-use-case-diagrams/ Conger,(2011). System Scope Diagrams. p.230, Figure 7.3: Retrieved from https://www.dlsweb.rmit.edu.au/toolbox/ecommerce/tbn_respak/tbn_e2/html/tbn_e2_devsol/ dfds/dfdrules.htm http://www.slideshare.net/ALATechSource/sample-project-requirements-document-libraryblog Udit Sehgal