Posted by: ahmedashfaque | June 11, 2017

Mock up screens: best way to design software products


Designing software products is one of the most difficult tasks. Not many people can actually create designs for good software products.

Software designs usually consist of user interface designs, component diagrams, class diagrams, object diagrams, statechart diagrams, object interaction diagrams, sequence diagrams, entity relationship diagrams etc. when you need to create a software product using object oriented design and programming.

When I design software products, I usually create all these types of software designs. Apart from software designs, i also create use case diagrams to model the software requirements.

The best way to design software products is by creating mock up screens first. I always prefer this way because mock up screens can be used to create all other types of software design diagrams easily. Why it is so? Let us understand.

Mock up screens depict user screens and what the user will do or receive information after computations. Mock up screens can also be easily understood by both the business domain experts and the project teams. So there are no chances of misunderstanding between the 2 parties.

Generally for a software product, there are user screens from where the user will provide inputs. These inputs are then used for computations and after computation, the user is provided with computed results on their user screens. The user screens where the user is supposed to provide inputs can be used to create classes easily. All the fields on a user screen become properties of a class or classes. The screens which show computed results can be used to model behavior of classes. So most of the classes and their members can easily be captured from the mock up screens.

You can also create relationship among classes from the mock up screens. For example, if a user screen where computed results are shown uses field data from more than one class then the classes having members corresponding to those fields will have some kind of relationship.

Similarly if one user screen needs inputs from the user to show another screen requiring user inputs on this screen again then the class which will be built corresponding to this screen will definitely will be a child class of the class corresponding to the first screen.

Thus you will end up creating all classes, their members and their relationships from mock up screens. From mock up screens you can also create all other types of software design diagrams easily.

Advertisements

Responses

  1. Thankyou for wonderful article. It has more Information in Your Website sap videos.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s

Categories

%d bloggers like this: