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.

Objective:

You will learn how to solve a question accurately and precisely. You will learn how to extract useful information from a given lecture to prepare for exams. You will get confidence to prepare for exams. Irrelevant/ambiguous/incomplete answers in the exams will reduce at some extent that will increase students learning. You will learn how to grasp latest knowledge.

GDB Topic

In the Requirement Engineering Phase of software development, does the role of Aspect Oriented Development is vital in gathering the requirements, considering the cross cutting concerns with respect to the functions and features associated with the functional requirement of the system requested ?

Give strong reasoning with or against the case given to you.

Views: 4281

Replies to This Discussion

Aspect oriented software development:-

Aspect oriented software development is an approach of software development for separation of concerns (SOC) in a proposed system. There are AOSD techniques that provide a way to modularize the crosscutting aspects [21]. By using these techniques the crosscutting concerns can be identified, Modularized, represented and composed in a systematic way [22].

AOSD is based the idea of an abstraction an aspect , Same like Object Oriented Software Development is based on the idea of object [23].

The Aspect oriented software development is a new discipline and aspect orientation is being promoted to progress through the all stages of software development life cycle including requirement, Design and development phase. A faultless software development process is the main aim of AOSD where crosscutting concerns are the main drivers of the software development through requirement to implementation [24].

AOSD promote a culture of developing software systems using techniques and tools that can be used in every phase of SDLC including architectural design of software system.

Requirements gathering: Effective gathering of requirements should be conducted by
developers using business-centric approach which breaks the language barrier between
information technology and business communities.
There are two main perspective of RAD approach to requirement gathering [13]:
1. The task-oriented business community, which supplies the development team with
information and feedback on system components and confirms that all requirements
have been filled
2. The system-oriented IT team, which organizes components, controls system
development, and checks for missing requirements.
Customers and developers are linked through a partnership with the use of these
perspectives. Both parties are able to understand the whole picture i.e. what are the main
components of the software, how they will interact with each other and how they will going
to be used [13

https://binbox.io/PMEes

1. The task-oriented business community, which supplies the development team with
information and feedback on system components and confirms that all requirements
have been filled

RSS

Looking For Something? Search Below

Top Trends 

Latest Activity

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

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