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

Description Of Waterfall Model IT Essay

Content
  1. Description of Waterfall model [W1]
  2. Selection of the correct methodology: -
  3. How waterfall model will be useful in development of "Smart Whistle blower" software?
  4. 3. 2 Component Wise Development Plan
  1. 3. 3 Analysis and Test Plan
  2. Unit Testing
  3. Integration Testing
  4. Core Functionality
  5. Type of Testing
  6. Intrusion Diagnosis and Security alarm module
  7. Administrator terminal module
  8. Enhanced Functionality
  9. Type of Testing
  10. Chat and Mobile Notification Module
  11. Web module for remote access
  12. Special Functionality
  13. Type of testing
  14. View Live Consumer Screen or Display screen shots of Consumer Screen
  15. Install/ Uninstall Individual Programs
  16. Project Name
  17. Test ID
  18. Testing Module
  19. Testing method
  20. Date
  21. Name of tester
  22. Description of Module
  23. Pre condition
  24. No.
  25. Actual Input
  26. Expected Result
  27. Actual Result
  28. Status
  29. (Cross/Fail)
  30. Error
  31. Correction Measure
  32. Project Name
  33. Test ID
  34. Testing Module
  35. Testing method
  36. Date
  37. Name of tester
  38. Description of Module
  39. Pre condition
  40. No.
  41. Actual Input
  42. Expected Result
  43. Actual Result
  44. Status
  45. (Forward/Fail)
  46. Error
  47. Correction Measure
  48. Project Name
  49. Test ID
  50. Testing Module
  51. Testing method
  52. Date
  53. Name of tester
  54. Description of Module
  55. Pre condition
  56. No.
  57. Actual Input
  58. Expected Result
  59. Actual Result
  60. Status
  61. (Pass/Fail)
  62. Error
  63. Correction Measure
  64. Project Name
  65. Test ID
  66. Testing Module
  67. Testing method
  68. Date
  69. Name of tester
  70. Description of Module
  71. Pre condition
  72. No.
  73. Actual Input
  74. Expected Result
  75. Actual Result
  76. Status
  77. (Go away/Fail)
  78. Error
  79. Correction Measure
  80. Project Name
  81. Test ID
  82. Testing Module
  83. Testing method
  84. Date
  85. Name of tester
  86. Description of Module
  87. Pre condition
  88. No.
  89. Actual Input
  90. Expected Result
  91. Actual Result
  92. Status
  93. (Go/Fail)
  94. Error
  95. Correction Measure
  96. Project Name
  97. Test ID
  98. Testing Module
  99. Testing method
  100. Date
  101. Name of tester
  102. Description of Module
  103. Pre condition
  104. No.
  105. Actual Input
  106. Expected Result
  107. Actual Result
  108. Status
  109. (Go away/Fail)
  110. Error
  111. Correction Measure
  112. Project Name
  113. Test ID
  114. Testing Module
  115. Testing method
  116. Date
  117. Name of tester
  118. Description of Module
  119. Pre condition
  120. No.
  121. Actual Input
  122. Expected Result
  123. Actual Result
  124. Status
  125. (Go/Fail)
  126. Error
  127. Correction Measure
  128. 3. 4 Analysis on success criteria
  129. User Requirements
  130. Research and Analysis
  131. Functionality of the system
  132. Project management
  133. Testing
  134. Documentation
  135. 3. 5 Work Breakdown Structure
  136. Total Duration 34 weeks
  137. Planning(Estimated time: four weeks)
  138. Implementation (Estimated time: 10 weeks)
More...

The software strategy that is probably going to be used during the development of the project is the Waterfall Model. Its strong things lie in the actual fact that it is sequential, so there would be no dilemma on the steps and the procedures are upright down--no need to stress about so many conditions while working on a project. Also, this type of model will pack up on very much documents. Therefore, such tends to be great for future code revisions and guide.

This model assumes certain requirements to remain static through the life of the job, so there exists little or no chance of adding new changes to the program once work commences. If changes are attempted to be integrated it contributes to more confusion and additional delays. The waterfall model is a sequential software development process. Following are the stages of waterfall model.

Conception

Initiation

Analysis

Design

Construction

Testing and Maintenance

Description of Waterfall model [W1]

The waterfall model, as explained above, offers numerous advantages for software creators. First, the staged development circuit enforces self-discipline: every stage has a precise start and end point, and progress can be conclusively discovered (by using milestones) by both merchant and customer. The emphasis on requirements and design before writing an individual type of code ensures minimal wastage of commitment and reduces the risk of plan slippage, or of customer goals not being attained. Obtaining the requirements and design taken care of first also increases quality, so it's much simpler to catch and correct possible defects at the look level than at the testing stage, after all the components have been included and searching for specific problems is more complex. Finally, because the first two stages end in the production of a formal specification, the waterfall model can aid efficient knowledge copy when associates are dispersed in different locations.

Selection of the correct methodology: -

For selecting the appropriate methodology a comparative evaluation was done between various kinds of models i. e. Waterfall Model, Spiral Model and RAD to determine the best model for the proposed system.

Table 3. 0: Contrast of different Models

How waterfall model will be useful in development of "Smart Whistle blower" software?

Based after the comparison chart the programmer critically evaluates the waterfall model with distinction to the development of the system "Smart Whistle Blower"

First of most as the task that we will be doing can be an academic project rather than an extremely financial task so less risk is involved. Waterfall model is ideal for such type of jobs because in other models like spiral there is risk analysis in every step that'll be complicated and even expensive.

Secondly since the waterfall model employs simple and sequential software development methodology so that it will be help full for the builder to complete each step with excellence and then move on to the next step.

The modular procedure in waterfall model is also one of the extremely important factor that it's been chosen. Here the developing of the software will be finished first and then coding will be started. So, implementation phase is only going to be started when the planning is completed. This will be helpful because the builder can know the machine well enough to what direction to go with the coding part by looking at the interface designs.

Another essential aspect for which waterfall model is chosen for this type of software development because as it is a Network Monitoring and Management Software development so there could be some modules that may be dependent on a component that needs to be developed first. For instance while remote gain access to of client Computer, the software must have a module to first identify the PC and only from then on further functionality concerning on that client PC can be performed. So Waterfall model provides a modular testing strategy, like each module will undergo testing phase before it's been finished. This may further assist in interoperability issues and also integration of \one module with another.

Finally the requirements of this job demand high- quality fully efficient software. So waterfall model is most well suited for this type of short-span task of one calendar year because it comes after simple software development methodology in which Progress of system is measurable and pre-defined demanding sign-off of requirements is completed prior to starting of any component.

3. 2 Component Wise Development Plan

Gantt chart

3. 3 Analysis and Test Plan

In order to provide a fully functional, a highly acceptance error-free system, the machine shall involve a tremendous amount of evaluation or tests which must be achieved by various people (such as the person that the programmer is planning to interview) throughout the machine development. Plainly, a good assessment should follow a few important guidelines and it should be carefully planned. The main testing procedures which will be performed through the development of the suggested system will be based on the stages of the Waterfall Methodology. In this methodology the design stage is followed by the implementation phase. Right from this aspect of development the Testing steps starts. The methods of testing through the consecutive phases of Waterfall model are:

Unit Testing

As software assessment process, first the evaluation shall commence by undergoing unit testing for each and every modules that will pose a problem in understanding the logic. Unit trials ensures each module and function works properly. Quite simply, the system developer itself will be tester to perform the unit evaluation. Following are the features under which white box test will be performed.

Intrusion Detection And Alarm

Notification or Text message Module.

Administrator operation module

LAN line disconnected notification

Basically, the black-box screening approach treats the machine as black field or close package whereby the system tester is only going to know the formal inputs and projected results. Therefore, the system tester will not require to presenting detailed functional understanding of the system and as well as how the program actually finds those results. Actually, the machine tester tests the machine predicated on the functional standards those we directed at them.

Black Box evaluation will be performed on the following features:

Intrusion Detection And Alarm

Notification or SMS Module.

Administrator features module

LAN wire disconnected notification

Tester: Developer

Number Of testers: 1

Integration Testing

Different modules which is working together should be integrated and tested to check on their output. A bottom up way will be adopted to organize the assessments. Integration tests will be done on

Intrusion Diagnosis And Alarm

Notification or Text message Module.

Administrator operation module

LAN line disconnected notification

Tester: Creator, network administrator

Number of testers: 2

System Evaluation Next testing then shall continue towards system evaluation where in fact the software will be subjected to compatibility, security and performance evaluation.

Tester: Programmer, Network Administrator

Number Of testers: 2-3

COMPATIBILY Assessment: Compatibility screening would be the last step. This type of testing is necessary to check on whether software works with with all the operating systems. This testing will help to notify compatibility issues.

Core Functionality

Type of Testing

Intrusion Diagnosis and Security alarm module

Black Box Evaluation, Integration Assessment,

Black Box Testing, Unit testing

Administrator terminal module

Black Box Evaluation, System Screening Integration Testing

Enhanced Functionality

Type of Testing

Chat and Mobile Notification Module

Black Box Evaluation, Unit Testing

Web module for remote access

Black box testing, Integration Tests, System Testing

Special Functionality

Type of testing

View Live Consumer Screen or Display screen shots of Consumer Screen

Black Package Testing

Install/ Uninstall Individual Programs

Black Package Testing

USER ACCEPTANCE Screening: User popularity testing will be done to ensure that the users will be able to access all the information according with their needs efficiently and specifically.

This testing is the most important part of screening as it offers a synopsis of the acceptance of the system in market.

At last, the final level of the machine testing would be the benchmark tests or so-called alpha testing where the practical requirements would be evaluated to know whether the system is appropriate with a potential end-user. The tester itself will be offered real data used, not simulated data to look at the inputs and outputs of the machine and the as commenting the user's friendliness of the machine. This is done with questionnaires directed at users that test the machine. Some of the questions are:-

Do you find any difficulty of using the system or is the system ease to work with?

Does the system meet your need?

The entire user's reviews or the comment given by the tester will be well-documented for even more enhancement of the system.

Test Case -1

Project Name

Smart Whistle Blower

Test ID

001

Testing Module

Login authorization

Testing method

Unit testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Verifies a User

Pre condition

Page must be connected to database/file

No.

Actual Input

Expected Result

Actual Result

Status

(Cross/Fail)

Error

Correction Measure

1

Enter the correct username and password

Message (" login successful") and redirects to next page

2

Enter wrong username and password

Message("Login Failed!! ") and redirects back to the login page

Test Case -2

Project Name

Smart Whistle Blower

Test ID

002

Testing Module

Detection of machines in the network

Testing method

Black Field testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Detect machines in the network

Pre condition

LAN wire must be connected to the machine

No.

Actual Input

Expected Result

Actual Result

Status

(Forward/Fail)

Error

Correction Measure

1

Press the search machine button

Message ("machines detected") and listed

Test Case 3

Project Name

Smart Whistle Blower

Test ID

003

Testing Module

LAN wire connectivity

Testing method

Unit Testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Check if the system is linked to LAN

Pre condition

A LAN line must be there to carry out this test

No.

Actual Input

Expected Result

Actual Result

Status

(Pass/Fail)

Error

Correction Measure

1

Remove LAN wire

Message (" Particular system has gone out of network") and the client machine must get log off with its password change

2

Manipulate IP Address

Message (" Particular system has truly gone out of network") and your client machine must get log off

Test Circumstance 4

Project Name

Smart Whistle Blower

Test ID

004

Testing Module

Intrusion Detection and Alarm

Testing method

Unit & Integration Testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Checks when a storage area device is attached in customer PC

Pre condition

A LAN cable must be there to carry out this test

No.

Actual Input

Expected Result

Actual Result

Status

(Go away/Fail)

Error

Correction Measure

1

Insert storage space device in the dock available

To admin terminal Meaning (" Particular consumer has placed device in his system")

2

Insert storage device in your client Computer when admin unavailable in his terminal

SMS alert to Admin cell-phone "This user has inserted a storage space device in his system"

Test Circumstance 5

Project Name

Smart Whistle Blower

Test ID

005

Testing Module

Web-Login for remote access

Testing method

Unit & Integration Testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Whether the user is able to login from his mobile phone

Pre condition

WLAN or internet must be present at the point of login

No.

Actual Input

Expected Result

Actual Result

Status

(Go/Fail)

Error

Correction Measure

1

Open BROWSER. Provide Login Details

Message ("Login Successful") and redirects to the server software.

2.

Provide inappropriate login

Message (" Login unsuccessful") and redirects to same page

Test Circumstance 6

Project Name

Smart Whistle Blower

Test ID

006

Testing Module

Administrative terminal module

Testing method

Unit & Integration Testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Check various feature of the administrative terminal

Pre condition

Must be linked to your client machine

No.

Actual Input

Expected Result

Actual Result

Status

(Go away/Fail)

Error

Correction Measure

1

View Process

Message ("Order successful") and report on process

2.

Kill process

Message (" the process killed") and redirects to view process page

3.

Log off and change password

System logged off and the password is changed

4.

Restart

The machines restarted

5.

Shutdown

The machines are shut down

Test Case 7

Project Name

Smart Whistle Blower

Test ID

007

Testing Module

Enhanced & special feature module

Testing method

Unit & Integration Testing

Date

Feb 2011

Name of tester

Boris Borkakoty

Description of Module

Check various feature of the improved functionality

Pre condition

Must be linked to your client machine

No.

Actual Input

Expected Result

Actual Result

Status

(Go/Fail)

Error

Correction Measure

1

Chat notification

Chat message triggered and received

2.

View live or print display of customer machines

Client machine printing screen received

3. 4 Analysis on success criteria

The proposed requirements are nominal in quantity as well as in performance requirements. To evaluate on how successful this job is, these criteria are considered:

User Requirements

All the user requirements should be evidently described, and then only the project can be successful.

Evaluator: Supervisor and end user

Research and Analysis

The research and research should be achieved very carefully done so that the information provided in the project cab be verified and really should be appropriate. If the research will not be good, all your time and effort of making the machine is going in vain.

Evaluator: Evaluator

Functionality of the system

All the efficiency of the system should be well edged out at the last so that all the functions work very well during the demonstration. If any function is not developed properly then your project is a failure.

Evaluator: Supervisor and end user

Usability & HCI (Man Computer Discussion) Evaluation: System usability will be evaluated here. Could it be comfortable for users or network administrator to make use of the system? Are they easily in a position to communicate with the machine? Is every single module performing the desired functionality? Answer of the questions will tell the usability of system. "YES" answers means system approved usability rules.

Evaluator: Supervisor, Supervisee and End users

Project management

The project needs to be handled well so that all the aspects of the task development are taken well.

Evaluator: Supervisor

Testing

After developing the machine, the work is not over. System assessment should be done in order to check on if the system is free from errors and bugs or not. Following the testing one can say that the machine is fully useful.

Evaluator: Developer

Documentation

The documentation should be done in such a way that anyone who reads it recognizes it as well. It is the documents only which is the explanation of one's body. The entire paperwork standard should be carefully implemented.

Evaluator: Supervisor

3. 5 Work Breakdown Structure

Total Duration 34 weeks

Planning(Estimated time: four weeks)

Pre-proposal (Length: a week)

Identify Project

Prepare abstract PPF

Prepare draft proposal.

Finalize project subject.

Project standards (Length: 3 weeks)

Identify task task

Identify project scope

Identify Resources

Identify techniques to be learn

Select methodology

Prepare PSF

Prepare Research plan

Prepare Design plan

Prepare Development Plan

Prepare Test Plan

Prepare WBS

Prepare Gantt chart

System Research (Length: 14 days)

Perform major research (Questionnaire and Observation)

Academic Research

Research on the efficient regions of the project

Review of Literature

Categorize task modules

System Research and Design (Period: 9 weeks)

Analyze end user requirement

Analysis Use circumstance model

Draft Use case specification

Content Analysis

Interaction Analysis

Functional Analysis

Configuration Analysis

Analysis Course diagram

Analysis Collection diagram

Architectural Design

Navigational Design

Story Boarding

Prototype Design

Technical Learning (Length: 4 week)

Finalize programming languages

Learn the fundamentals for the utilization in the project

Identify third party tool and work on it

Implementation (Estimated time: 10 weeks)

Core Functionality Modules (Length of time: 3 week)

Analyze the module

Code the module

Perform unit tests on the module

Document the module

Enhanced Functionality Module (Length of time: 4 week)

Analyze the module

Code the module

Perform unit testing on the module

Document the module

Special Functionality Module (Period: 2 weeks)

Analyze the module

Code the module

Perform unit testing on the module

Document the module

Integrate all the modules (Length of time: 1 week)

Testing (Period: 3 weeks)

Perform integration testing

Perform system testing

Perform system integration testing

Perform user popularity testing

Documentation (Length of time: 14 days)

Develop End user Manual

Compile system documentation

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