Report on Systems Development and Procurement

Added on - 21 Apr 2020

  • 21

    pages

  • 4896

    words

  • 10

    views

  • 0

    downloads

Showing pages 1 to 6 of 21 pages
Systems Development and Procurement1Systems Development and ProcurementBy (Name)Course NameName of the ProfessorStudent’s NameDate
Systems Development and Procurement2Table of ContentsTask 1.........................................................................................................................................................3Executive Summary...............................................................................................................................3Background of the Study.......................................................................................................................3Literature Review..................................................................................................................................4Resources/Materials used for the system.............................................................................................4Potential Risks.......................................................................................................................................4Timeline/Work Breakdown..................................................................................................................5Task 2.........................................................................................................................................................6Methodology used..................................................................................................................................6Differences between the methodologies............................................................................................6Task 3.........................................................................................................................................................8DownTown requirement collection techniques...................................................................................8Interviews...................................................................................................................................8Use of questionnaires.................................................................................................................8Use of prototypes........................................................................................................................9Functional and Non-functional requirements.....................................................................................9Task 4.......................................................................................................................................................11Use case Diagram.................................................................................................................................11Use case Description............................................................................................................................12Task 5.......................................................................................................................................................14Proposed development methodology..................................................................................................14Modeling techniques............................................................................................................................15Modeling and development tools........................................................................................................15Conclusion............................................................................................................................................15Task 6.......................................................................................................................................................17Class Diagram......................................................................................................................................17Task 7.......................................................................................................................................................18References................................................................................................................................................20
Systems Development and Procurement3Task 1Executive SummaryDownTown Videos, wants to take advantage of the market by developing a state of theart system for renting movies and video games. In order to achieve this, the system to bedeveloped must include all the objectives to satisfy its customers better. Using the internet andthe World Wide Web it is determined to unite all its customers by providing excellent services toits customers.Background of the StudyAutomating processes in businesses has been a controversial issue that determines failureor success of a business. Most businesses nowadays have automated their process in order togain an edge over other businesses. Besides the ongoing growth in business, the current manualsystem in place at the DownTown videos doesn’t not provide means in which it can give properservices to its customers such as the keeping of inventory, keeping track of useful informationabout movies such as the movie titles, genre, and customer related information and so on. Thishas led to the loss of important information that is stored in print form. As a result, the businesshas faced stiff competition from other movie and game rental businesses around.Literature ReviewIn order to overcome this problem DownTown Videos is experiencing, it has been decidedthat an online rental system will solve their problem. The system will improve the servicestowards its customers by automating all the process to be undertaken while renting the moviesand games thereby gaining a competitive edge over its competitors. The objectives of the systemwill include;Store information about movies (genre, rental type, rating, cost, and producer).Create a nice user interface to improve customer interaction.To ensure that the rental system performs the operations in real time and ensure optimumutilization of resources.Extending video marketing to other areas.To help the management in making a decision about the store.
Systems Development and Procurement4Resources/Materials used for the systemTo make the project a success, a number of software and hardware materials will be needed tocomplete the system and meet its objectives. These includes:High-speed laptops or desktops.MySQL server to store data.An Integrated Development Software such as NetBeansProgramming language such as PHP, HTML, JavaScriptPotential RisksRisks can be defined as the changes that happen in the project management process that mayhave an influence on its development[CITATION Bar04 \l 1033]. There are many types of risks thatmay affect a system under development. In our scenario, we encountered some of the risks thatcould influence the development of the system. These could be:i.Technical risks - One of the main reason behind the risk could be because of therequirements that could change as per the customer. Since the project team involved eachand every stakeholder in the development of the system (i.e. customers and staff), it notedthat requirements had to change as per customer. Another reason was that in theintegration of different modules of the system we could have some problems. These riskwould, therefore, make the system fail and hinder its functionality if not taken care of.ii.Management risks – these are the risks associated with environments that are notconducive enough, insufficient hardware reliability and low effectiveness of theprogramming. The solution to this problem is that, if the team leader is working with ateam for the first time he/she should go through a testing period in order to familiarizewith the teamiii.Operational risks – the team leader should be aware of such risks that could lead to lossowing to inappropriate process implementation[CITATION Kar95 \l 1033]. These risks mayhappen as a result of inadequate resources, lack of resource planning, lack of teamcommunication as well as failing to settle the responsibilities.[CITATION QAr11 \l 1033].
Systems Development and Procurement5iv.External risks – these are factors that are not in control of the project team. These riskscan be in form of war, crime, bankruptcy etc. This poses a direct threat to the projectsince predicting, and controlling them tends to be difficult[CITATION Raf03 \l 1033].Timeline/Work BreakdownWith the help of a Gantt chart, we can provide a way in which we can plan, coordinateand track tasks that are related to the development of a system in a graphical manner (Clark, W).The system to be developed will include the following steps that are going to be followed asshown in the Gantt chart below:WeekActivity123456789FeasibilitystudyAnalysisDesignCodingSystem TestingSystemImplementationSystemMaintenanceDocumentationTask 2Methodology usedThe agile methodology makes use of agile teams that work directly with customers inorder to appreciate the objectives and give a result without much delay and in an incremental
Systems Development and Procurement6manner (Cockburn, 2002). The iterative methodology, on the other hand, uses a completelydifferent path as compared to agile methodology. In this method, the software is developedthrough recurrent cycles and in lesser portions at a time (Basil et al. 1975).One of the methodologies used in the agile category is the Scrum methodology. It is aframework that assists people can solve intricate problems while delivering products of highvalue creatively (Schwaber et al. 2002). On the other hand, extreme programming delivers shortand frequent parts of the system under development in an iterative form. The customer isinvolved during unit testing and reviewing the code. (Beck, Gamma 2000).Differences between the methodologiesThere are some of the differences between scrum and extreme programming as explained below:To start with, the team undertaking the scrum method do not encourage any changes intheir sprints. When the sprint gathering is over and a pledge is done to bring the set ofproduct backlog items, these items are left unaffected till the conclusion of the sprintwhereas extreme programming teams are prone to more changes in iterations.In the scrum, the time interval between sprints ranges from two weeks to a month-longwhereas iterations in extreme programming are in between one to two weeks long.In the scrum, the owner of the product determines the workload by prioritizing theproduct backlog from the one with the highest priority descending to the one with leastpriority. In Extreme programming, however, everything is prioritized by the customer. Ituses the first come first served notion.DownTown video system would likely use Extreme Programming methodology. The projectmanager has realized that in order to retain and attract more customers, the system must givemaximum satisfaction. This methodology then integrates both the customers and the projectdevelopment team. This gives the customers knowledge of how the system is like and gets achance to give their own ideas. This makes them feel that they are part and parcel of the systembeing developed.Another issue that needs to be taken care of is the time that is needed to complete the system.The team must, therefore, be as efficient as possible while delivering the product. In order toachieve this, the project leader must stress teamwork. This methodology assumes that customers,
desklib-logo
You’re reading a preview
card-image

To View Complete Document

Become a Desklib Library Member.
Subscribe to our plans

Download This Document