PLAGIARISM FREE WRITING SERVICE
We accept
MONEY BACK GUARANTEE
100%
QUALITY

A Well Detailed Spiral Model Information Technology Essay

The life cycle model most likely preferred or suited to Sales Order Despatch Application system is the Spiral Life Cycle Model.

The Spiral Life Circuit Model is a software development way combining components of both design and prototyping in a much more thorough and understandable phases.

The spiral life routine combines the iterative mother nature of prototyping with the handled and systematic areas of the waterfall model, therein providing the prospect of speedy development of incremental versions of the program. On this model the program is developed in some incremental releases with the first periods being either newspaper models or prototypes. Later iterations become increasingly more complete editions of the merchandise.

A WELL Complete SPIRAL MODEL

The spiral life pattern model typically has 6 task locations:

i. Customer Communication

ii. Planning

iii. Risk Analysis

iv. Engineering

v. Building and Release

vi. Customer Evaluation

All the above mentioned tasks needs to be addressed through the development of the Sales Order Despatch Software.

1. 1 Customer Communication

This activity region basically is due to knowing the client and establishing an efficient communication and gathering the requirements of the system to be developed. Customers therefore would be known as the management of the Sales Order Despatch System. These requirements can be accumulated using several fact finding techniques. The techniques used because of this system would be:

Questionnaires

A study will be simply completed on decided on Sales Order Despatch Request current individuals. This study would help us understand what the finish users of the SODA would wish from the new system. And by positioning any current problems they may be facing as at the time the survey has been carried out can help in enhancing the new system and tackling such problems in the new system.

Interviews

In this particular fact finding approach, different degrees of workers and physiques of the organisation would be interviewed to be able to obtain a suitable and preferable view of the system to be integrated. Such problems being encountered in the current system also need to be addressed, and those problems must be surpassed by the new computerized system.

The most significant people who be interviewed would be the Managing Director of Fizzypop Plc and major end-users of FizzyPop plc responsible for your day to day activities.

The purposes of these fact findings are to understand the efficient and non-functional requirements of the machine.

1. 2 Planning

Once all the necessary information is collected through the interviews and questionnaires, they should be dealt with as requirements.

Also the system must be developed within a limited time and budget. In this stage an initial budget will be built to get a tough idea on what the final cost is to implement the system. This primary cost will change from the ultimate budget due to numerous varying factors.

Also a deadline must be given by the restaurant as to when they want the system executed. A Gantt chart must be developed to keep an eye on the progress of the machine. This will ensure that the system is completed and delivered promptly. This a view of the gantt graph which the programmers and analysers will use to screen the improvement of the system to be developed:

2 4 6 8 10 12 14 16 18 20 22 24 26 28 30 32

Here will be the functional requirements determined for the machine:

Functional Requirements

Functional requirements will be the requirements needed for the new computerized system to function properly. Listed below are the efficient requirements for the Sales Order Despatch Program system:

* Allow the end-user to designate the customers carbonated drinks and delivery requirements via an intranet web page.

* Able to edit, add to the job sheet online.

* Allowing personnel and management to see and produce information of packed items, via their interior networking infrastructure (i. e. , their intranet).

* Customers order is been verified against current capacity, stock availability and delivery times.

* Receive confirmation of the delivery date and related billing information

* The information system must be integrated using their current customer and distribution database.

* The machine will, from time to time, supply the company with precise reviews of customer profiles (amount of customers, types of drink purchased, and current earnings).

* 1. 3 Risk Analysis

In this particular process region, all possible hazards to be experienced are been identified. A risk possibility impact matrix should be also put up in order to understand the consequences of the potential risks better. Whereby Risk categories have been divided in to 2 sections, particularly Technological and Management, and here are types of such risks:

* Management Risks

o Computer illiteracy within end-users

o Does take time for end users to be more comfortable with the change of preliminary system to current system

o Misuse of developed system might trigger unnecessary expenditure on maintenance

o Insufficient team Support

o Inadequate time to complete project

o Inadequate cash/ Final expenses higher than preliminary budget

o Disclosure of company information

* Technological Risks

o Power Failures are vulnerable to loss of data

o Because of inappropriate management Data Problem / Loss of Data can occur

o There could be Intruder Problems from hackers.

o Hardware Failures.

o The Super fast evolving and change in software.

Initially after getting all the risks for the machine, it has been mentioned down that the following risks that have an actual hazard to the Soda pop system are brought up below:

* Inadequate time and energy to complete project

* Inadequate cash/ Final bills higher than initial budget

* Data Problem / Loss of Data

* Intruder Attacks

* Hardware Failures

* Misuse of Equipment

1. 4 Anatomist:

This job region is to create the machine with the gathered requirements information using chosen tools and coding techniques decided on. A sample prototype can be designed as well in this stage.

The program writing language you can use to build up the Sales Order Despatch Request SODA could be Java and ASP. NET Since java is an extremely popular programming language using its own GUI. While ASP. NET is a online programming language which is also platform independent with JAVA so that it would be easy making future amendments to the system, in case the machine hardware is evolved or prepared to be assessed again.

SQL server 2008 can be used to create the data source for the Bottling companies. It is much easier to create and link dining tables and create questions using SQL server 2008 and you will be able to manage all customer and bottling information, including record keeping of customers going to the web site.

1. 5 Construction and Release

This is the stage where the prototype of the machine that was initially designed in the previous stage would be helped bring into life by coding the machine.

Once the coding is carried out, the system has to test to see if it fulfills all the requirements. Testing can be carried out using test of test situations and then your actual productivity is matched against the expected output of the above mentioned system.

Once we could through with evaluation and it matches the given anticipations, the final paperwork is prepared plus a training manual demonstrating the customer on how to use the system. Technical support will also be provided along with working out manual.

1. 6 Customer Evaluation

This is the task region whereby opinions is been obtained from the management of FizzyPop Plc. Set up developed system is up to their expectations is discovered in this level. This may be determined as the ultimate level of the task if the machine is satisfactory by the FizzyPop plc. But. If it is not accepted therefore you have to state it is back to task region one, Customer communication, by getting the info needed to do amendments and understanding what the client wants in the system.

QUESTION 2

The goal of every software engineer in software engineering is gaining toughness for quality products with regards to the characteristics of such products. A couple of laid down set of qualities specifically linked with system dependability features such as security, basic safety, problem tolerance; quality that makes for convenience of use, such as usability, adaptability, and quality; and quality that facilitates and makes future enhancements and maintenance easy. There is certainly some agreement about the capabilities define software quality and dependability over a range of products. These meanings provide the bottom knowledge that individual quality products are prepared, engineered, analysed, measured, and enhanced.

There a wide range of dependability measurement attributes that might be put on the Soda pop system, but only few of such characteristics of stability measurements would be explained below. These capabilities have been selectively chosen because of its high contribution to Sales Order Despatch Program SODA specifically:

1. Efficiency/ Performance of the system

2. Accuracy

3. Dependability

4. Usability

2. 2Efficiency/ Performance of the system

Performance/ Efficiency of something, is a set of attributes that bear on the relationship between the level of performance of the software and the amount of resources used and under stated conditions. Resources can include other software, hardware, services of working and users for maintenance and operation. This attribute have 2 major features specifically: Time and resource behaviours.

And if a processing results requires a very high undertaking processor and lots or RAM to display the processed final result under 3 secs, that can be an indicator of poor resource performance.

In other words even if the prepared results are appropriate to its solitary term, it still requires excess time and resources, it will simply affect the entire quality of the machine.

.

2. 1 Accuracy

Accuracy is an attribute of software that handles the provision of right or arranged results and its results. The question to be determined next is how appropriate the machine performs.

For example, an individual enters drink specification Hill dew using the Add function in the databases, and the machine exhibits results for Drink specs of only Mirinda or Malta, that implies an inaccurate system. This happens due to poor programming and system developing.

Overall an inaccurate system means the quality of software is poor and then the end-users (FizzyPop plc) will never be pleased with the complete software.

2. 4 Dependability

After the machine has been made for FizzyPop plc And it includes shown to be efficient, effective, user friendly and safe, we still have to worry about how reliable the machine could be.

That is to say that Dependability basically is how dependable the system carried out would be, which has many features plus some of those features are:

* Maintainability

Normally following the system is integrated and sold to FizzyPop plc, it must be looked after, and this maintenance will be done by the users of SODA. Maintenance will usually include updating the machine software, taking backups. All of this will be educated to an individual through the training phase, but this also must be easy to do.

* Reliability

FizzyPop plc would most probably during the day, and the machine may also be on and operating so long as FizzyPop exists. it might only be transformed when further development process is been completed and ready to implement.

NOTE: The machine must be able to operate of these times without and accidents or system failing.

* Availability

The system must be able to be started up within a short while, and prepared to use. Concerns must be taken care of immediately as and when the user needs them, that is the basic notion of availability. The system must be ready to make use of on the users demand.

2. 3 Usability

Usability is a couple of attributes that put up with on your time and effort necessary for use of something, and on the individual examination of such use, usually assessed by the user of the machine.

The system developed for FizzyPop plc should be user friendly and learn. The user involved with your day to day function of the machine, does not really need to be very good technically. Which means system must be designed in a way it easy to comprehend for users who'll be using the machine. All error text messages must be in simple understandable English with less complex jargon. Therefore in the event of any errors the system user can overcome the situation by themselves. Any new customer of the Soda pop system can have an experience and understand how the machine works on their own. Which will be a very good sign of a user-friendly system, in other words a good quality system.

Also an exercise session must be provided to the users of Soda pop in order showing them about how the system works. A manual will also be given, in any case, if there are any problems in the machine that requires any attention, SODA users (FizzyPop plc. Staffs) can research the manual for details.

CONCLUSION

The spiral life circuit model has been chosen to develop the system so the final product developed for FizzyPop plcwill very few or no problems will be found at all. This model makes sure that all the potential risks included will be recognized and looked after before being paid to the Bottling Company known as FizzyPop plc. Since the spiral model uses a rotating style, it means that all requirements are discovered, and the system designed fulfills the specifications to be able to be sure SODA users are content with the system before the system is delivered to them. This spiral way of creating the machine is also somewhat costly to FizzyPop plc in comparison to developing the system using other methodologies, but its results is much deserving.

In summary of the stability measurement attributes, maybe it's said that, the program which is most efficient, effective and user-friendly would be bad in conditions on quality if it has low dependability qualities, such as, taking too much time to start-up, regularly freezing up/ crashing and needing high end technological training for users to keep the system. If it is also a very trustworthy system, but with poor efficiency, performance and an awful user interface. you won't be a good quality system either.

Finally we have concluded by expressing that the machine developed for FizzyPop plc must be perfect in every of these attributes; any defect or failing in any of these attributes will compromise the entire software quality for the machine.

More than 7 000 students trust us to do their work
90% of customers place more than 5 orders with us
Special price $5 /page
PLACE AN ORDER
Check the price
for your assignment
FREE