This is my first time to setup the blog and would like to share what my experience for software system development. My experience may not 100% follow the standards but it is just what I thought based on my experience.
Ok. let's start now..
Today, I would like to say about prototyping. From this topic, you may think that how could develop a system without prototyping. Yes, it is quite difficult without prototyping but what I said is try to minimize the dependency to rely on Prototyping. In terms of presentation, prototyping is easy to present the "real" system to user. However, it will limit the user's mindset because everything is setup. What they do is just follow the screen flow, the field shown in the screen. It may hidden some important function such as interaction with other modules, intergration...
When we discuss with user on the prototyping, user just focus on Screen, not real situation..
From my opinion, it is better to use the UML tools to build up the diagrams (such as use-case, sequential diagram..) and discuss with user but no prototyping at same time. Actually, it is a tough job for user to imagine the system without a "real thing" but it still better to convince them to follow it. It is because this is the only method to make the user think the system in the detail, not just based on the screen to determine what they need.
Honestly, this approach takes longer time during design phrase but minimize the risk under the implementation. As I mentioned earlier, this approach will let both developers and user understand what the system will done but not just a imagination. Prototyping makes things looks "real". However, it looks real only..
skip to main |
skip to sidebar
2 comments:
This is what UML are for. But u are damn right about the user, they cannot imagine the system without a getting a grap on the "real thing". How are u going to solve it?
i like your blog ....
Post a Comment