Before you begin to implement the needs of each part, you don't have to complete, detailed design for the entire product. However,
Before you have encoded, you must design each part. Design planning will be beneficial for large difficulties (there are many internal components interfaces)
And interacting systems and developers have no experienced items) (McConnell 1998). However, the steps described below will
Thanks to all items:
• Establish a rugged architecture for subsystems and software components that support support during maintenance.
• Explicitly need to create object classes or functional modules to define their interface, functionality, and collaboration with other code units.
• Define the intended function of each code unit based on a good design principle of strong cohesive, loose coupling, and information hidden design.
• Make sure your design meets all the features and does not include any unnecessary features.
When developers transform demand into design and code, they will encounter uncertain and confused places. Ideally,
Developers can go back to customers along the problem that occurs and gets the solution. If you can't solve the problem right, then developers
Any assumption, guess or explanation must be written as a document and reviewed by the customer representative. If you encounter
Many such problems, then these demands are not very clear or specific before the developer has achieved demand. in
In this case, it is best to arrange one or two developers to review the remaining needs before the development work will continue.
