4-1
System development technology
4-1-1 Process of system development
Reference
Service contract
A “service contract” is a contract that is
formed when the party placing the order
presents terms to the contractor regarding what they want to be delivered and
when, as well as the remuneration for
the finished product, and the contractor
accepts those terms.
Systems used in business operations are expected to perform the necessary
functions properly, but must also be easy for the user (system user department) to utilize.
It is important for the department developing a system to survey/analyze
requirements in cooperation with the various departments that will use the
system, and reflect the results into the system under development.
System development does not necessarily have to be carried out internally,
and may also be outsourced to a company that specializes in system development.
A “service contract” is a typical method for forming an agreement when
system development is outsourced to another company.
The general procedure for developing a system is as shown below.
Requirements definition
Determine the functions required of the system.
System design
Design the system based on the requirements definition.
Development
(Programming)
Develop the system based on the design details.
Testing
Check that the designed/developed system operates
properly.
System acceptance
Verify that the designed system operates according to the
requirements.
System operation/
maintenance
Resolve any issues the user (system user department)
encounters during system operation.
Reference
Need for review
For each system development process,
a “review” must be conducted. Reviews
check/confirm that there are no bugs
(errors) in the system or design, and
serve the purpose of improving quality
by finding any potential bugs and rectifying them.
Reviews may be conducted by the individual developer, a small project team,
or by all those concerned.
Although it is effective for the developer
to conduct a review, it is beneficial for
persons other than the developer to
conduct a review as well. An outside
perspective allows for an objective
check, which makes it possible to catch
bugs that go unnoticed by the developer.
115