Lesson 13 Introduction to Programming Student Resources
Write the problem statement
Download 0.83 Mb.
|
- Navigate this page:
- Write the requirements
- Code/test/fix the first version
- Design the next version of the program
- Deploy/maintain/evaluate the first code release and plan for the next release
Write the problem statement: This phase establishes a big-picture view of the intended project and determines its goals. This process may involve software users (called end users) who provide ideas for improving the project. This phase also includes conducting preliminary research to see whether the proposed solution is cost effective. Write the requirements: This phase is for analyzing the needs of end users and translating project goals into specific, practical requirements. Design the first version of the program: In this phase, developers describe in detail all the features and operations of the system or product to meet the needs defined in the planning phase. The design serves as a type of blueprint for the project and helps detect potential problems in the plan before programming is started. This phase often includes the creation of a prototype that shows how screens will look and how processes will flow. Code/test/fix the first version: This phase involves the writing and debugging of code to create an alpha (first) version of the software. 
Design the next version of the program: After adjustments are made to the alpha version, a beta (second) version is designed. End users often play a key role by helping to test the system or product in this phase. Code/test/fix the next version: In this phase, the beta code is created, tested, and fixed. At this point, an independent quality-assurance group may be employed to try to break the code. These people usually start by asking the question, “If I don’t do what the program asks, what happens?” Deploy/maintain/evaluate the first code release and plan for the next release: After final adjustments have been made to the beta version, what is sometimes called a “gold master” is put into production (manufactured) and released to the public (or to a specific customer) for installation and actual use. Then planning begins for the next product release. 
This process is iterative—in other words, after you complete step 7, you need to “circle back” and work through the steps again, starting with step 1. In a commercial programming organization, the process continues to iterate as long as the software product is supported in the marketplace. Rarely is a program released to the public without some undiscovered bug. Directory: ourpages -> auto -> 2017 2017 -> Senior Division Solutions 2017 -> Avant garde adademy of broward 2017 -> Have you always wanted to go to space camp? Dreamt of becoming an astronaut here’s your chance! 2017 -> Atlanta, georgia-april 2017-a total solar eclipse occurs when the moon lines up between the earth and the sun-an extremely rare and beautiful event 2017 -> United states history and geography unit 1: The Rise of Industrial America 1877-1914 2017 -> 1. 1: Analyzing Categorical Data 2017 -> Out-of-Field Notification to Parents/Guardians English 2017 -> Modern History Notes 9-21-2017 Entertainment 2017 -> The secret of change is to focus all of your energy, not on fighting the old, but on building the new 2017 -> The Berlin Conference 1884 Simulation Historical Context Download 0.83 Mb. Share with your friends:
|