Latest Activity In Study Groups

Join Your Study Groups

VU Past Papers, MCQs and More

We non-commercial site working hard since 2009 to facilitate learning Read More. We can't keep up without your support. Donate.

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.

Important Instructions:

  • Your answer should not exceed than 200 words.
  • Use the font style “Times New Roman” and font size “12”.
  • Your answer should be relevant to the topic i.e. clear and concise.
  • Do not copy your answer from Internet or any other source. Such answers will be marked Zero (0) and may damage your grade in the course.
  • You cannot participate in the discussion after the due date via email or MDB.

 For any further queries regarding GDB, email at cs504@vu.edu.pk.

Views: 5193

Replies to This Discussion

Well done,  PariFozu

I am very thank full all of the students who discussed  here their ideas and experience.  

PARI SIS

GDB SOLUTION:

I think that I should prefer the previous company software because that the previous company software is already launched  in the market and already doing a good business

all people can purchase that software easily because it is affordable and every body can purchase it and use easily and also know some privacy about that previous company software   but in contras the new company have less experience in the market about software related they want to sell   very high price software in the market but people

are not satisfied the company of new one as they known that new company software is

more advantages and good qualities as they know but they prefer previous company's software because that software doing their much work in very efficient way that have to do new one.   

pari sis ka blkul right hy 

most wlcm

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.

Requirements analysis topics

Stakeholder identification

Contract-style requirement lists

Measurable goals

Prototypes

Use cases

Subject: GDB
Assalm-o-Alikum. Sir kindly explain this line shortly:
"you have an ethical responsibility of confidentialityto your previous company"
Does it means that previous company have restricted us from providing their software to any other company. If it is the case then after some small changes in that software it is prohibited to provide it to other company. Also are their some rules or restrictions like this in professional life of a software engineer.
Post Your Comments
Other Students' Comments: 0

Instructor's Reply:

Walikum Salam.
                       Dear student!
                                            It means that if you work in an organization and then leave. You can not leak their data because:
                      
1. Data is related to that particular company and they have copy rights. If you leak or give any other organization, they can challenge you in the court.
2. It is an ethical responsiblity of an employee not to share company's data to any other company. 
3. As a software engineer, it is your responsibility to keep data confidential whether you are in that company or not. This is one of the basic professional ethic of software engineering profession.
4. Moreover, it is a question about your loyality.
Just see in your real life, you do not pass the secrets of one friend to an other or a doctor does not discuss one patient's problem to other patient because this is against professional ethics.

Regards 



Student's Message: Msg No. 571666
Subject: about gdb
a.o.a
respected sir
we are confuse about the gdb topic please help us in detail so that we can understand the main purpose of topic
sir please answer me as soon as possible. 
Post Your Comments
Other Students' Comments: 0

Instructor's Reply:

Dear student!
                     First of all, you dont need to confuse about it. Its nothing but a very simple scenario. You are working in a company. Company has taken a project for development. While working there, you see that they are working in wrong direction. As same project was developed in your previous company differently.
Now what you will do ? If you dont correct them, project will fail and cost would high.
You can not tell them about previous company's working way as its against professional ethics. (If you work in an organization and then leave. You can not leak their data. )
So how will you resolve it ? You are required to simply provide a way that how you can solve it by considering both things.

Think about it, map it to real scenario and answer the question on the basis of your understanding and basic knowledge of Sooftware Engineering.

Regards

check all for clearing concept..

Student's Message: Msg No. 571685
Subject: GDB
Sir if someone leaks the data of any company then how can it come to know that its data has been leaked. Also in software development database is used but the records in tables of database are not necessarily same for bath companies. Now its the matter of development of software, how data is being used in development?
Post Your Comments
Other Students' Comments: 0

Instructor's Reply:

Dear sir!
              Yes. It is not necessary that if you leak some data, other company will know. But it is a project related to millions of worth. Then they will know as its matter of copy rights.
Even if company never know about data leakage, employee is not justified to do. As I said earlier. It is an ethical duty of every employee to keep his company's data confidential. Its matter of loyality and right/wrong judgement.



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.


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.


Requirements analysis topics
Stakeholder identification
Contract-style requirement lists
Measurable goals
Prototypes
Use cases

RSS

Looking For Something? Search Below

Latest Activity

VIP Member Badge & Others

How to Get This Badge at Your Profile DP

------------------------------------

Management: Admins ::: Moderators

Other Awards Badges List Moderators Group

© 2021   Created by + M.Tariq Malik.   Powered by

Promote Us  |  Report an Issue  |  Privacy Policy  |  Terms of Service