Page 212 - DCAP302_ENTERPRISE_RESOURCE_PLANNING
P. 212

Enterprise Resource Planning




                    notes          storage requirements

                                   Identify  organization,  content,  and  size  of  databases,  types  and  frequency  of  updating  and
                                   inquiries, and the length and rationale for record retention.
                                   control requirements


                                   Identify validation rules, security requirements, and adaptability requirements for the system
                                   input, processing, output, and storage functions.
                                   Finally, the overall system definition needs to be refined to prepare detailed software specifications
                                   covering:
                                   1.   Information flow (DFD)
                                   2.   Interfaces
                                   3.   Functional requirements

                                   4.   Design requirements &constraints
                                   5.   Coding structures
                                   6.   Testing criteria
                                   A Software Requirement Specifications (SRS) which is the basis for software development gets
                                   prepared at this stage.

                                   12.4.2 Design considerations

                                   System analysis describes what a system, should do to meet the information needs of users.
                                   Systems design specifies how the system will accomplish this objective and generates the system
                                   specifications that satisfy the functional requirements identified in the earlier phase.
                                   The design should be traceable to the analysis model. The design should “minimize the intellectual
                                   distance”  between  the  software  and  the  problem  and  should  be  structured  to  accommodate
                                   change. The design should be reviewed to minimize conceptual errors.
                                   The overall structure of the software is the architecture of the software to be built.
                                   It is a representation that enables a software engineer to:
                                   1.   Analyze the effectiveness of the design in meeting its stated requirements,

                                   2.   Consider architectural alternatives at a stage when making design changes is still relatively
                                       easy, and
                                   3.   Reduce the risks associated with the construction of the software.

                                   The design phase translates the SRS into a workable solution and defines the following:
                                   1.   Database Design defines the database structures and the data dictionary.
                                   2.   Menu Design defines the alternate options and selection mechanisms
                                   3.   Input Design defines the user interfaces to capture the information. It covers two aspects -
                                       Input Form Design and Input Screen Design.
                                   The input form is the basic input that is received from the external entity. In today’s environment,
                                   depending on the application, it is possible to provide a screen to the external entity to input this
                                   information. However there are situations where such a thing is not feasible and hence an input






          206                              LoveLy professionaL university
   207   208   209   210   211   212   213   214   215   216   217