Bonanza Offer FLAT 20% off & $20 sign up bonus Order Now
COMP23311
UK
The University of Manchester
Creating a prototype for any application is crucial as it enables users to test the application prior to the real development process. During developing a prototype, experts must be involved to avoid making mistakes on the application developed (Menzel, Schönherr, and Tai, 2013). In this case, the FASAM application prototype will capture the possible features that a sound system will have a thorough development in a prototype form whereby the experts will play a critical role
The Fasam system has the following objectives for development purpose
Refers development to create the appearance and function of an application to mimic the original application. The prototype plays a crucial role in the development of an actual application by capturing essential features of a system. Therefore, a prototype needs to have all features of an original application. For FASAM to work efficiently, there is a need for it to have essential functionalities that make it to be the best in the market (KovaÄević et al., 2014). The following are illustrating functionalities in the system
Refers to dividing software into smaller sequential or parallel steps to improve design, project management, and product management. This process in also known as software development lifecycle, whereby various steps of developing a software are dealt with in in an order manner step. The most modern development of the software is the agile development process. Besides agile, there are other software development methods like water, prototyping, iterative, rapid application, spiral development, and extreme programming.
The figure below illustrates various stages of the rapid software application process, including requirement planning, user design, construction, cutover. The user design section has subsections like the refinement, test, and prototype process.
In the user design section, several activities of preparing software take place. For example, testing and prototyping, and refinement activities of the software take place for delivery.
During prototyping, different versions of the software can rise up to create the best model.
This model of system development requires the use of prototype and iterative development. This software development method requires planning of the software developed to capture all needs; Rapid application development depends on the customers to give requirements through meetings done on workshops or nay another focus group.
Usually, this process requires an early testing process of iterative to be used in system development, continuous integration, reuse existing prototypes, and finally, rapid delivery.
This is the first stage of the Rapid software development process. Stakeholders and other users meet and share the best requirements needed to be implemented in a project.
Thus, a process, the scope of the project is determined. During this stage, clients communicate to determine goals and the expectations required from a project when finished. This might include stating the current problem faced, defining the requirements, and finalizing a project's requirements. At this stage, the FASAM system users will be reared to deliver the current issues they have regarding the system and the ways they hope a system will make their lives better when using it. Proper research must be done in this stage in order to avoid the future stoppage of software development (Meyr, Wagner and Rohde, J., 2015). Some of the requirements that can be gathered include the type of sprinkler to be installed, type of alarm system, cost involved in the development process, legal acceptance, timeline of the project, prototype to be developed, the structure of the organization and level of technology suitable.
This process is critical as designing various prototypes of the project. The users and the preferred requirements and setup of the system is taken into consideration; the clients and developers at this stage work together to ensure that the project id delivered on standard without facing any issue; The bugs arising from the designs are removed through an iterative process by developers designing a system while the users evaluate its efficiency in solving problems; The system features like the controller’s location, electricity system model, sprinkler design and location are determined in this stage in order to deliver the best software, (Chernikov, 2018)
This is the actual process of developing a model system of FASAM. Since the designing process captures the essential features and eliminated uses features, developers use relevant information to come up with a good model of development. The process usually starts by preparation, goes to program and application development, coding, integration testing, unit testing, and system testing.
Programmers develop testers a word together to ensures that everything is delivered according the standard designed (Wencel and Glorius, 2013).
Refers to the final stage of the rapid development process, the stage mainly involved implementation of a program; it involves testing, conversion, and changes over to the new system. All final changes are made in the FASAM system to ensure that everything is delivered according to the clients' expectations. At this stage, the expectation goes to the large building area where FASAM will be installed and checks the nature of the facility (Min et al, 2018). The necessary requirements are presented in order for everything to be delivered in time.
Rapid software development is a good technique for developing software applications that enables designing and solving problems a final user might solve when using the software despite its goodness. The approach has got also its weakness when system developers used it in the development process. Below is an evaluation on the merits and demerits of this method in the system development process.
Flexibility: The requirements of the projects can be changed at any stage of the project in case of change by upgrading Rapid software development the prototype continuously
Prioritizes and encourages the customer’s feedback: End-user and stakeholders are given the biggest priority in the process of software development i.e., their feedback and queries can make a prototype be change
Reviews are quick: Unlike Waterfall methodology, whereby more time is taken, hear the reviews are made quickly and updated onto the application
Development time is less: The method concentrated on actual application development than other non-essential activities which take more time like research
More productivity can be achieved with less man input: This method of system development concentrate on use of develops, system analysist who multitask in order to finish the project in time
Easy integration: During actual development, there is idea of integration with another system since this method is more flexible
Rapid software development also has some disadvantages during the development process.
Strong team collaboration: This method of system needs members to work together in harmony to achieve the goals
Not good for large teams: Building big teams becomes a big challenge since the whole process is synchronized to small project
Need most highly skilled programmers and developers: Since the prototype keeps changing, experience is very essential.
The process always knees the user requirement throughout the process
The methodology is sometimes Comparex compared to other methods of software development
The application that is developed must be able to be divide into modules for the probability of
Refers to describing what the user does to the system, such as actions that a user must perform, which are defined in the user requirement document. These requirements are written by end-users and the system user.
The system's user requirements must be chronologically arranged in a format to capture essential elements of the user requirements (Balatsoukas 2015). This can be attained by arranging them in the format of introduction, program requirement, data requirement, and life cycle requirements.
The figure below illustrates how the system will be been seen from the user side. As the figure shows. The screen will be split into several options for the users to enter data. On the top side of the design shows the section for the emergency case of the system. Each zone letter represents a kind of danger that can be expected on the system. On the other hand, the intermittent tone will indicate the zone indicator on the system.
The main goal of this type of prototype is to simulate the incoming signal into reading a text file.
This object is responsible for emergency actions on the system.
In this case, the input will come in the form of text when the signal is sent in sensory equipment.
The alarm signal will have to be verified because some sensory may fault due to tireless operations.
Suppose a control area is monitored by a person at a given point. In that case, the inspection will be done visually, for example, using a camera to check hazards or visit the places that have hazard situations to confirm. On the other hand, if a person does not monitor the system, a second signal will have to be weighted for confirmation purpose
System development process prototype has got its own benefits and challenges to any organization. The rapid software development process plays a critical role in developing a prototype by ensuring that the building structure is safe and residents are not challenged extremely during the prototype's high trying time.
The process analyzes the building where a system will be installed and breaks it down into small manageable tasks of any particular.
Despite many good features of this type of system development, there are also challenges experienced by this form of the prototype development process. The list below illustrates the kinds of challenges experience due to this process of system development
Menzel, M., Schönherr, M. and Tai, S., 2013. (MC2) 2: criteria, requirements and a software prototype for Cloud infrastructure decisions. Software: Practice and experience, 43(11), pp.1283-1297.
KovaÄević, M., Madić, M., Rapid software developmenttovanović, M. and RanÄić, D., 2014. Software prototype for solving multi-objective machining optimization problems: Application in non-conventional machining processes. Expert Systems with Applications, 41(13), pp.5657-5668.
Meyr, H., Wagner, M. and Rohde, J., 2015. Structure of advanced planning systems. In Supply chain management and advanced planning (pp. 99-106). Springer, Berlin, Heidelberg.
Chernikov, V., 2018, November. Approach to rapid software design of mobile applications’ user interface. In 2018 23rd Conference of Open Innovations Association (FRUCT) (pp. 1-7). IEEE.
Wencel-Delord, J. and Glorius, F., 2013. C–H bond activation enables the rapid construction and late-stage diversification of functional molecules. Nature chemistry, 5(5), p.369.
Min, J., Nothing, M., Coble, B., Zheng, H., Park, J., Im, H., Weber, G.F., Castro, C.M., Swirski, F.K., Weissleder, R. and Lee, H., 2018. Integrated biosensor for rapid and point-of-care sepsis diagnosis. ACS nano, 12(4), pp.3378-3384.
Balatsoukas, P., Williams, R., Davies, C., Ainsworth, J. and Buchan, I., 2015. User interface requirements for web-based integrated care pathways: evidence from the evaluation of an online care pathway investigation tool. Journal of medical systems, 39(11), pp.1-15.
Are you looking for custom writing help? Then you have come to the right place. We have handpicked the best subject matter experts to help you with your academic tasks. Whether you need help with an academic poster or you need a ghostwriter, we have got your back. Our essay writing service has garnered immense popularity from all over the world. This is mainly due to the client-centric services and reasonable prices we offer. We also provide online exam help to students and help them score good grades on the paper hassle-free. Get paper help from PhD-qualified experts and boost your grades like never before.
Upload your Assignment and improve Your Grade
Boost Grades