Information Technology and Ethics/Steps for Software Development
Clients give programmers an abstract view of what they need the program to do, at this time IT Professionals communicate whether or not the client's specification are able to be reached. Sometimes Clients have requirements that contradict one another and this may make it difficult for the programmer to do their job. At this point, it may best for the programmer to provide the client a demonstration of code to communicate better what the client wants or expects. Scope document states what the client expects from the project, describes the objectives and costs. If the project is developed outside of the company or organization the scope could be used as a legally binding document. The scope should contain the following:
- The Project Name
- The project definitions
- The project owner, sponsors, and stakeholder
- The problem statement
- The project goals and objectives
- The project requirements
- The project deliverable
- Cost Estimates
Programmers may also want to review current systems (if any) to identify any existing procedures that may continue in the new system. During the planning process IT professionals may want to replace the hardware in order to facilitate the new system.
Development and TestingEdit
During the development phase, IT workers develop system interfaces, screen layouts and how the system would generate reports. Users would then review and approve these features. Software designers may decide to input redundancy has to protect the system from failure if an error occurs. Programmers then complete the program and test the software. The testing ensures the software works as specified in the project scope. If the project fails to meet a milestone, the budget, or the project requirements the clients may sue IT professionals for any of the following:
- Breach of Contract
Implementation, Documentations and TestingEdit
The implementation process begins with the client and IT workers coming together to create a strategy of implementation. This strategy covers the who, what, when, where and how. Then the process of correcting and converting data to the new system begins. Procedures for both users and IT workers are created. Documentation should contain the following:
- instructions to end-users
- flowcharts data flow diagrams
- Archive, purge, and retrieval
- Backup, storage, and recovery
The organization's IT workers and End-users should be trained in the use and maintenance of the new system. The system is then retested to make sure the system works as expected and to discover any bugs.
During the maintenance phase, they correct bugs discovered either through the testing phase or through use by end users. Maintenance may also happen when the companies have new requirements of the system. The maintenance phase may be the most time consuming of all because you may need to add code that does not fit the original design. If the maintenance cost becomes out of control it may be more prudent to rebuild the system then continue with the one currently used.