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.

CS504 GDB 'Software Engineering-I (CS504)' will be open on Wednesday 10th July, 2013 and it will be closed on Friday 12th July, 2013.

Discussion Topic

                             Software Architecture is the organizational structure of a system. Architecture can be recursively decomposed into parts that interact through interfaces, relationships that connect parts and constraints for assembling parts. Parts that interact through interfaces include classes, components and subsystems. Whether software architecture plays any role to satisfy the non-functional requirements? Justify your answer with strong arguments. 

Read the instructions carefully before sending your comments:

  1. GDB will have weight-age of 5% of your total subject marks.
  2. Your discussion must be based on logical facts.
  3. You should post your comments on the Graded Discussion Board & not on the Regular MDB. Both will run parallel to each other during the time specified above.
  4. Your comments should be relevant to the topic i.e. clear and concise (Maximum 5-8 lines answer).
  5. Books, websites and other reading material may be consulted before posting your comments. (Do not copy the material as it is.)
  6. No extra time will be given for discussion.
  7. You cannot participate in the discussion after the due date or through e-mail.

Views: 3458

Replies to This Discussion

Muhammad zubair thanks for sharing ...keep it up 

Attention Students: You don’t need to go any other site for this assignment/GDB/Online Quiz solution, Because All discussed data of our members in this discussion are going from here to other sites (Other sites Admins posted with fake IDs at their sites :p ). You can judge this at other sites yourself. So don’t waste your precious time with different links.

Researchers believe that quality attributes can primarily be achieved in a conservative manner in terms of cost and time if software architecture is evaluated or assessed with respect to the specific quality attributes prior the implementation. In this approach emphasis has been given on the forward engine`eering rather than the reverse engineering approach in order to save time and cost. In this proactive approach an initial version of the software architecture is designed. Then it is evaluated with respect to the quality requirements by using a qualitative or quantitative assessment technique. Using the assessment results, the estimated quality attributes are compared to the values in the specification. If these are satisfactory, then the design process is finished. Otherwise, the architecture transformation or improvement stage is entered. This stage improves the software architecture by selecting appropriate quality attribute optimizing or improving design solutions. When applying architecture design solutions, generally one or more quality attributes are improved whereas other attributes may be affected negatively. By applying one or more architectural design solutions, a new architectural design is created. The newly created design is evaluated again and the process is repeated, if necessary, until all non-functional requirements have been satisfied as much as possible.

The choice is your..........

Game Over

prhaakoo bachy..........itna parh k b game ocer.........???????

Software Software Architecture performs a vital  role and part in non-functional requirements. Architecture partitions your system into smaller parts, which should make estimation more structured, more accurate. You can also use architecture to support development, for example different teams or individuals having responsibility over different architectural subsystems, and controlled incremental test/release of subsystems from the bottom up. Bottom line is that development of a code base with a defined and enforced architecture will be quicker and more predictable/manageable - all else being equal - and improve many of the non-functional aspects of your project. A system incorrectly designed for non-functional requirements can meet all the functional requirements, but turn out to do it inefficiently as well as in a manner very difficult to control (thus not meeting the non-functional reqs.).

How do software architects deal with non-functional requirements?

The full results of our exploratory study on how software architects deal with non-functional requirements (based on a set of interviews with software architects) were presented at the RE’12 conference (full paper is available here and the summary/slides can be browsed below)

What was the motivation of this work? Research papers on software architecture often include sentencens like:

“[NFRs] play a critical role during system development, serving as selection criteria for choosing among myriads of alternative designs
“the rationale behind each architecture decision is mostly about achieving certain NFRs”
“quality attribute requirements strongly influence a system’s architecture”
but the problem is that there is very little evidence that this is really how software architects work in practice. Therefore, we set out to see if we could confirm or not this assumption.

Some of the observations that can be derived from the analysis of the interviews’ data were quite surprising (for full details and the threats to validity see the full text linked above, in the following we single out some simplified results):

In fact, nobody had a permanent software architect role. Instead, they played the role of software architect (and others simultaneously) depending on the project
There is a lot of confusion regarding the exact meaning of several non-functional requirements
Non-technical requirements (price, license, provider) are as important as the technical ones, i.e. the SW architecture can never be the ideal one but the one that satifies all these non-technical constraints).
The software architect, and not the client, is the one that decides which NFRs are needed
System compliance with the NFRs is hardly ever verified
No tool support to manage the NFRs is used.

non-functional requirements define the operation of a system. these are important for any system. a system in which all non-func. requirements are not considered would fail. software architecture plays an important role to satisfy non-functional requirements as it is organizational structure of a system and it is incomplete without non-functional reqs.

hey Jigsaw ! i wanna play a game. you have to give this GDB's answer simply as yes or no. otherwise you'll have to face some musik :-D 

i think software architecture plays any role to satisfy the non-functional requirements because from book "Software architecture must address the non-functional as well as the functional requirements of the software system.  So software Architecture performs a vital role and part in non-functional requirements. " 

plz koi idea share karay

 @ Mohsin Latif

Sorry for late reply answer is yes. n m ready to play game. But this time choice is mine.


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

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