Software Design
Name:
Institution:

Software Design Summary
Software design is to produce a plan (model) that represents a workable (implementable) solution to a given problem. Software design is not procedural, but it is empirical or opportunistic that is an exploration of the potentially very large solution space. Quality software should be developed based on the users’ requirements. A right software development methodology should be employed in order to develop a right product such as Waterfall modeling.
Design process are steps that enable the software developer to describe, analyze all aspects of product to be developed. It should not suffer from the ‘tunnel vision’ that is the developer should consider alternative approaches judging each as per the user’s requirements. It should also be traceable to its analysis model since one design can be traced to many requirements, so they should be a clear means of tracking them. Design should use the backlog of existing system but not inventing the wheel. However, there should be uniformity and integration in the design and should regularly be reviewed to avoid semantic errors. The design should be developed in such a way that it can be altered when need arises. It should also be assessed to ensure software quality.
Software design considerations are: compatibility in that the system is design to operate in any platform that is not limited to a specific environment. The design should be extensible; in that new elements can be added easily without altering the core functionality of the architecture. It should be scable; it should adapt well to the increasing number of users or data. It should also be robust design; that is should work under pressure i.e. low memory capacity.
Software design should be done well with the real time system which processes concurrent inputs from many sources. They have real time