[Okta Webinar] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 404
  • Last Modified:

How to understand requirement and design

Some times for me understanding the requirement is bit challenging and then next step development which is some what manageable with some help.

For example requirement as below it is taking 5 days to understand below requirenemt and may be one more week to develop it with some forum help.


I am creating objects ObjectDef and FieldDef

Then I am creating an example input file ObjectDefs.txt

Then i will create initialization method that reads that files and creates

a map <className, ObjectDefinition>

so that i can look up after that just by the className to get the ObjectDef for it using reflection.

Then I parse the text file and send to one other application/system.





where, how i get these kind of complex requirements, examples, end to end scerios to master these concepts quickly and implement effectively. How to design effectively before development.

please advise
Any links resources ideas highly appreciated. Thanks in advance
0
gudii9
Asked:
gudii9
1 Solution
 
Ken ButtersCommented:
I don't there is such a thing as a place to go to, to learn how to understand requirements for a given project / assignment.

The reason for that, is that no two assignments are the same.   The best I think you can do is to have a good understanding of the tools you use to build your project.  

I think a lot of what you are talking about will come naturally with experience.  As you become more familiar with the tools you have, it will be easier to see how the pieces need to fit together to arrive at a workable solution.

Some of the concepts you just mentioned...

Creating objects
Creating a  Map
Looking up a map using reflection

These items can be learned/taught fairly easily.  What is more difficult to grasp right away is to understand when they should be used, and when they should not.

Reflection for example is a concept that I believe should always be avoided if possible.  Use of reflection is usually a result of a poor design.  Your requirements for your project seem suspect to me.

Most requirements should state the need to accomplish a particular goal .  Using reflection and using Java Maps is not so much accomplishing a goal, but rather specifications on HOW to accomplish that goal.

It's important to understand, that at that point, you are not being given requirements, you are being given designs.  Those are two completely different things.

It might be better to get a good grasp on what goal needs to be accomplished, what needs to happen.... then the designing part comes in answering the question... how those goals can best be accomplished.
0

Featured Post

Concerto Cloud for Software Providers & ISVs

Can Concerto Cloud Services help you focus on evolving your application offerings, while delivering the best cloud experience to your customers? From DevOps to revenue models and customer support, the answer is yes!

Learn how Concerto can help you.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now