Your company has got a project for developing a software system. A similar software system was developed in your previous company. You discover that your company's interpretation of requirements is different from the interpretation taken by your previous company. Cost of project will tremendously increase if ambiguities in requirements are not resolved. You have also an ethical responsibility of confidentiality to your previous company. Discuss what you should do in such a situation?
Note that GDB will remain open for 2 days only (from 11th Feb to 12th Feb, 2013) and no extra time will be given for posting the answer. Therefore, make sure that you submit your answer within the given time.
Also before posting your answer, keep the following important instructions in your mind.
For any further queries regarding GDB, email at email@example.com.
Plz share your idea
plz help me in this gdb
in this gdb, we have to tell our opinion what we will do for such sistuation
i think, one person served in two different software company, we have to tell about the requirements issue? that different in both the companies.
software company interpretation of requirements
Requirements analysis, also called requirements engineering, is the process of determining user expectations for a new or modified product. These features, called requirements, must be quantifiable, relevant and detailed. In software engineering, such requirements are often called functional specifications. Requirements analysis is an important aspect of project management.
Requirements analysis involves frequent communication with system users to determine specific feature expectations, resolution of conflict or ambiguity in requirements as demanded by the various users or groups of users, avoidance of feature creep and documentation of all aspects of the project development process from start to finish. Energy should be directed towards ensuring that the final system or product conforms to client needs rather than attempting to mold user expectations to fit the requirements.
Requirements analysis is a team effort that demands a combination of hardware, software and human factors engineering expertise as well as skills in dealing with people.
YEH HI BATANA HAI K KIA AAP IS SITUATION MAY PREVIOUS COMPANY K RAAZ APNY PASS HI RAKHYN GAY YA IS SOFTWARE MAY USE KARYN GAY.
thanx rameez, dear tell me what should we write for this situation? means it is better to use your previous expreince here?
i will never use due to requirements are different
the requiremnts are different?
HERE IS IN GDB
You discover that your company's interpretation of requirements is different from the interpretation taken by your previous company
but the project is same....interpretations are different..and we have to remove ambiguity while keepkng previous company's secret....what to do?