We are here with you hands in hands to facilitate your learning & don't appreciate the idea of copying or replicating solutions. Read More>>


Looking For Something at vustudents.ning.com? Click Here to Search

Starting Date Wednesday, August 08, 2018
Closing Date Thursday, August 09, 2018

Topic/Area for Discussion

The software architecture discipline is centered on the idea of reducing complexity through abstraction and separation of concerns. Software architecture contains different views including user view, developer view, tester view, owner view and concurrency view etc. Each view contains different subsystems and their respective interaction through a well-defined interface. Designing of each view requires time, cost and resources. What do you think which “View” is important to design if  product owner don’t focuses much on non-functional requirements to build up. Justify your point of view with solid points.

+ Click Here To Join also Our facebook study Group.

..How to Join Subject Study Groups & Get Helping Material?..


See Your Saved Posts Timeline

Views: 3432

.

+ http://bit.ly/vucodes (Link for Assignments, GDBs & Online Quizzes Solution)

+ http://bit.ly/papersvu (Link for Past Papers, Solved MCQs, Short Notes & More)

Replies to This Discussion

this is from midterm syllabus. check 1 to 5 lectures in handouts.

pleeeeeeeeeeeeeeez solution

see reply

Lecture No. 03 ()Page # 22

 Analyze it whether correct or not  only pare-3 is answer is this solution or not? Please comment coz not confirm

  1. Functional Requirements: The next level of detail comes in the form of what is called functional requirements. They bring-in the system’s view and define from the system’s perspective the software functionality the developers must build into the product to enable users to accomplish their tasks stated in the user requirements - thereby satisfying the business requirements.

 

  1. Non-Functional Requirements in the last section we defined a software requirement as a document that describes all the services provided by the system along with the constraints under which it must operate. That is, the requirement document should not only describe the functionality needed and provided by the system, but it must also specify the constraints under which it must operate. Constraints are restrictions that are placed on the choices available to the developer for design and construction of the software product. These kinds of requirements are called Non-Functional Requirements. These are used to describe external system interfaces, design and implementation constraints, quality and performance attributes. These also include regulations, standards, and contracts to which the product must conform.

Download file from descriptipn 

CS504 GDB Solution

Wrong

shabbir bhai ap sahi upload kar dy cs504 ki gdb

i think its from lec no 23 Architectural view

#CS504 GDB Idea 

listen brother!!!

they asked this question

What do you think which “View” is important to design if  product owner don’t focuses much on non-functional requirements to build up. Justify your point of view with solid points.

the solution file u send is not correct.. we have to describe only one view which is imp and suitable.. 

pleeeeeeeeeeeeeeeeeeez right solution bta do koi

RSS

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

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