A case study on supermarket management system

A racing shell study on supermarket management governanceINTRODUCTIONProblems can be solved by musical arrangements. carcasss approach is an organized way to deal with problems. In this dynamic world, a wide variety of remains maturement methodologies switch evolved over the years, each cloth with its own strengths and weaknesses (Paul, James Peter, 2004). This report impart centralize on waterfall role through analyze the serve well of EQs supermarket management frame development.SYSTEM bread and butter CYCLE placement manner roll is a structured process of underdeveloped and maintaining organizations. It lists all processes and sub-processes required while developing a outline. A combination of various activities in arrangement development is referred as schema development lifecycle (Kriinen and Vlimki, 2008).1. PHASES OF SYSTEM DEVELOPMENT LIFE CYCLE1 .1 SYSTEM STUDYSystem development life cycle starts from system of rules study. The system study separates in two phases. Firstly, a survey will help the intentioner to identify the scope of the system. Secondly, a depth investigation will help the blue instiller understand exploiters requirements and problems. Generally, a system proposal will carry out by analyst and offer to exploiter to ensure the content is correct (Steven Glenn, 2005). EQ delineate YDL as a small sized supermarket. The owner of YDL wanted to p ar employee (keep two people at most), monthly report can be presented faster and establish a membership system.1.2 FEASIBILITY STUDY base on system study, feasibility study takes place. The proposed system should be cartridge clip- attempted during this phase in four aspects workability, requirement fitness, effective use of resources and the court effectiveness (Steven Glenn, 2005). The main objectiveive of this phase is achieving the scope. To achieve the scope, EQ sour the SMS have six main functions, they are sales, reporting, goods ordering, membership manage ment, expired offers and memorial management. This proposed system only of necessity two people, which are cashier and breed manager. Order goods and generate financial statement can be through with(p) by the system automatically. Therefore, a sub-system called membership management was added into this SMS.1.3 SYSTEM summaryIf a new system is decided to develop, the next phase is system analysis. It is a depth investigation based initial investigation and user requirements. Detailed data fertilize diagrams (DFDs), data dictionary, logical data structures and toy dog specifications should reflect user requirements. Identification of data store, sub-dividing of complex process, and manual processes besides should be included in system analysis (Steven Glenn, 2005).EQ naturalized its project schedule, listed all major activities and tasks in WBS (Work Breakdown Structure), and the deliverables and milestones were also announced in the schedule. Task DescriptionDurationAssign ed componentTask InputOutputRequirementsSpecify requirementsGeneral introduction most the system1 week vigilance squad aggroup liaisonsA requirements record, A architecture object document (system design document), A object design document, A ladder plan, A project plan.System/subsystem, and requirements overview2 weeksDocumentation TeamRequirements elicitationGeneral constraints, assumptions and dependencies2 weeksFunctional requirements2 weeksExternal interface1 weekNon-functional requirements1 weekMilestones R5 documentsDesign Design the architecture of the systemlSystem organization design1 week selective information processing system architecture TeamA architecture design documentSystem source encryptSubsystem design2 weeksArchitecture TeamAsystem design documentDesign the user interfacesubstance abuser interface design2 weekssubstance abuser Interface TeamA object design documentMilestones DSystem source cipher evolutionDesign the specific objects of the systemDatabas e and configure the server1 weekDatabase TeamSystem source codeSystemUser interfaceProgramming3 weeksUser Interface TeamLayout design3 weeksUser Interface TeamDesign the specific objects of the systemConnection between subsystems1 weekControl TeamMilestones DeThe system that is available to useValidationImplement the systemTest the user interface1 weekUser Interface TeamSystem source codeA document about the problems that the system still needs to be worked onTest the database1 weekDatabase TeamEvaluate the systemList the functions and problems1 weekDocumentation TeamMilestones VA document about the problems that the system still needs to be worked onEvolutionValidate the system vary the user interface1 weekUser Interface TeamA document about the problems that the system still needs to be worked onFinal systemAdapt the database1 weekDatabase TeamAdapt and improve the systemRecheck the whole system1 week focusing Team Documentation TeamFinal systemA document about the functions that the system can provideMilestones EFinal system can be provided to clientSource http//www.docin.com/p-41243574.html Source http//www.docin.com/p-41243574.html1.4 SYSTEM objectSystem design is the most crucial phase in system development lifecycle. Generally, the design advances in two demonstrates general design and comminuted design. In general design process, the features of the system will be condition costs and benefits of these features will be estimated. In detailed design stage, computer oriented work starts at number one. Structure design becomes the blue print of system solution to those problems mentioned in system analysis phase. Furthermore, the courseming spoken language, the platform, input, outturn and processing specifications will decided in detail in this stage (Steven Glenn, 2005). Several tools and proficiencys utilize for designing are (Steven Glenn, 2005) Flowchart Data flow diagram (DFDs) Data dictionary Structured English Decision elude Decision t ree Based on the scope of this supermarket and proposed system, EQ used C/S deterrent example as development model. The source code were written in JAVA, Server unenviableware and software environment ironware IBM System x3200 M2. The x3200 M2 offers the latest quad-core Intel Xeon processor (up to 3.16 GHz/12MB/1333MHz), 4 GB shop (DDR II 800MHz), expansion slots (2 PCI (32-bit/33 MHz),2 PCI-Express (x8,x1), Remote Supervisor Adapter II), 4.0TB SATA HDDs hard drive. Software Microsoft Windows Server 2008, MySQL Cluster 7.0, Avast Anti-virus Server 4.8.1091, JDK 6 Update 16 with NetBeans 6.7.1 (E-Qun, 2009). Source http//www.docin.com/p-41243717.html Source http//www.docin.com/p-41243717.html1.5 CODING TESTINGAfter designing, the whole system should convert into computer understanding language. The programmer uses computer understanding language to write programs to coordinate the data movements and control the entire process in the system (Steven Glenn, 2005). Before implem enting the whole system, a test run is do to remove all bugs and measure the stability of the system (CMS, 2009). Firstly, individual units of the system should be tested. Any uncertainty happening must be record and debugged. Then, in compliance with test plan, a given set of test data will put into the system. The outputs of the test run should be analyzed. If theres any output did not match the expected output, the errors in the particular program or system should be identify and fixed and further test should be done until the outputs match the expected results (Parkin, 1997). Modular development technique was used in this coding and testing phase. EQ divided the programmers in two team, database team and user interface team. Each team focus on their own area. Source http//www.equn.net/product_1.asp Source http//www.equn.net/product_1.asp1.6 IMPLEMENTATIONDuring implementation phase, the system is loaded onto the users computer. Then, user training starts. Generally four top ics will be introduced to users execution of the package, data input, data processing and reporting. After users are trained, computerized running(a) begins at following two strategies (operational) parallel run or pilot run. Parallel run agency in a certain period, twain systems (i.e. manual and computerized system) are executed in parallel. Pilot run means the new system installs in parts. Some parts executed first and ran in a defined period. Other parts will be implemented only if the results satisfied the expected results (New York State Office, 2009). After cardinal days training, two employees from YDL had mastered the operational skills. In the later month, manual working and computerized working were running in parallel to avoid the potential failure of system. 1.7 MAINTENANCEMaintenance means error correction and get ahead during the systems working life. Because of there always have some errors found in the system, system review is necessary to note and correct th ese errors. In addition, from system review, the developer can know the full capabilities of the system, required changes and the additional requirements. If a remarkable change needs to be executed, a new project has to be set up and proceed through all the life cycle phases (New York State Office, 2009). Currently, EQs supermarket management system is running in YDL. The supermarket had reduced 2 members. Nearly 500 people were registered as members. Moreover, the owner of YDL wants to turn his business concern to chain-store operations. EQ has started to evaluate this project.DISCUSSIONAccording to Paul Davidson et al. (2003), waterfall model fits the situations where most appropriate that project has clear objects and solutions, the requirements are comprehensive and constant and etc. In this case, the lifecycle of this supermarket management system shows that E-Qun Web-Studio used waterfall method. This framework type is linear Those deliverables and milestones were measurab le. The whole project was divided into phases emphasized on planning, time management, target dates and system implementation at one time maintained control of project through using extensive documents much(prenominal) as project plan, test plan, etc. CONCLUSIONTo sum up, the lifecycle for information system development is mainly make up of eight aspects. They are system study, feasibility study, system analysis, system design, coding, testing, implementation and maintenance. Linear type is the simplest framework to develop the system (Paul et al. 2003). In small information system, if the system is not extremely complex, requirements are stable and can be identified easily, project team is less experienced and project schedule is unambiguous, it is strongly recommended that this project uses waterfall method as the develop methodology (Paul et al., 2004).REFERENCESAlter, S and Browne, J, 2005, A Broad View of Systems Analysis and Design, Communications of the Association for nur ture Systems, Volume 15, 2005, pp. 981-999, CMS, 2009, Testing Framework Overview, Centres for Medicare Medicaid Services, in stock(predicate) at http//www.cms.hhs.gov/SystemLifecycleFramework/Downloads/CMSTestingFrameworkOverview.pdf Accessed at 23th Dec, 2009 Davidson, P, Hedrich, R, Leavy, T, Sharp, W, Wilson, N, 2003, study Systems Development Techniques and Their Application to the Hydrologic Database Derivation Application, the Centre for Advanced Decision escort for Water and Environmental Systems, Available at http//cadswes.colorado.edu/PDF/RiverWare/DavidsonLV2002.pdf Accessed at 28th Dec, 2009 E-Qun Web-Studio, 2009, or so Us, E-Qun Online, Available at http//www.equn.net/aboutus.asp Accessed at 29th Dec, 2009 Fisher, P, McDaniel, J Hughes, P, 2004, System Development Life Cycle Models and Methodologies Canadian Society for International Health security measures Course in Health Information System, Module 3 System Analysis Database Development, Part 3 Life Cy cle Models and Methodologies. Available at http//famed.ufrgs.br/pdf/csih/mod3/Mod_3_3.htm Accessed at 14th Dec, 2009 J. Kriinen and A. Vlimki, 2008, Impact of Application Lifecycle Management A Case Study, Enterprise Interoperability III, New Challenges and Industrial Approaches, Springer capital of the United Kingdom Press, London New York State Office, 2009,System Implementation, Project Management Guidebook, Release 2, Available at http//www.oft.state.ny.us/pmmp/guidebook2/SystemImplement.pdf Accessed at 22th Dec, 2009 Rodney Parkin, 1997,Software Unit Testing, IV V Australia, Available at http//www.ivvaust.com.au/UnitTesting.pdf Accessed at 20th Dec, 2009