Verified Document

Software Requirements Analysis: Implications For Article Critique

On this aspect of agent-based SDLC performance, both approaches are limited in terms of their applicability and scalability. The reliance on heuristics can only go so far with the embedding of business, technical and organizational elements into the overall structure of an SDLC methodology (Kumar, Goyal, 2011). The reliance on an agent-based model fits well with the development of modules that are designed to align with these innately unquantifiable aspects of the context of an SDLC project, and further, the use of the completed application. Web Services is more utilitarian in its definition of functionality and its need to be pervasive and accessible as an inherent design criterion (Maamar, Mansoor, 2003). This utilitarian approach to defining Web Services is in contrast to the highly specified configured parameters of an agent-based approach to SDLC-oriented heuristics (Kumar, Goyal, 2011). While each has its unique strengths and must be selectively applied base don the business objective of the software being developed, each need to make significant gains in quality management and self-optimization before these technologies will be used more pervasively in enterprise software development. Both technologies continue to make progress towards the objective of being self-optimizing yet there is still the need for aligning intelligent agents to specific SDLC requirements and Web Services as a state engine layer across the entire...

Parts of this document are hidden

View Full Document
svg-one

These differences in approaches also point to the nascent use of autonomic computing to ensure self-configuration, self-optimization, self-healing and self-protection is attained throughout the intelligent agent lifecycle and its integration to the SDLC framework (Kumar, Goyal, 2011). In comparable terms the operating modes of agentification, identification, correspondence, notification and realization are within the Web Service architecture used for agent-based SDLC development (Maamar, Mansoor, 2003). Both of these approaches also rely on an intelligent state engine that can provide and predict the need for specific types and approaches to decision making based on the SDLC requirements. Both however are still in their formative approaches to defining the overall structure and approach to managing integration with specific business rules and requirements.
References

Kumar, A., & Goyal, V. (2011). Software requirement analysis enhancements by prioritizing requirement attributes using rank based agents. International Journal of Computer Science and Information Security,, 9(8), Retrieved from http://www.docstoc.com/docs/93385123/Software-Requirement-Analysis-Enhancements-by-Prioritizing-Requirement-Attributes-Using-Rank-Based-Agents

Maamar, Z., & Mansoor, W. (2003). Design and development of a software agent-based and mobile service-oriented…

Sources used in this document:
References

Kumar, A., & Goyal, V. (2011). Software requirement analysis enhancements by prioritizing requirement attributes using rank based agents. International Journal of Computer Science and Information Security,, 9(8), Retrieved from http://www.docstoc.com/docs/93385123/Software-Requirement-Analysis-Enhancements-by-Prioritizing-Requirement-Attributes-Using-Rank-Based-Agents

Maamar, Z., & Mansoor, W. (2003). Design and development of a software agent-based and mobile service-oriented environment. E - Service Journal, 2(3), 42-58.
Cite this Document:
Copy Bibliography Citation

Related Documents

Software Development Life Cycle
Words: 2835 Length: 10 Document Type: Essay

Software Development Life Cycle Agile Software Development Agile software development is a popular software development process or methodology that has gained a lot of popularity in the recent years due to its effectiveness and ease of use. Firstly, it encourages collaboration and teamwork throughout the life cycle of development and this makes it easy to plan and implement. Agile software development is all about breaking a task into small chunks that make it

Software Development Life Cycle SDLC
Words: 3695 Length: 12 Document Type: Essay

Software Development Life Cycle ( SDLC) Explain Requirement process ( in SDLC) in detail. Why is this exercise important? Requirements engineering is a fundamental activity in systems development and it is the process by which the requirements for software systems are identified, systematized and implemented and are followed through the complete lifecycle. Traditionally engineers focused on narrow functional requirements. Now it is being argued by Aurum and Wohlin (2005) that focusing only

Software Development Life Cycle
Words: 1559 Length: 5 Document Type: Essay

Software Development Life Cycle Social Media Software Implementation Project Social media is an important aspect of every business today because it gives companies a unique chance to understand the customers better and to interact with them at a more personal level. A wide range of social networking tools are used by companies to attract customers to the products and services offered by the company and this makes social media software implementation essential

Software Documentation Is an Integral Part of
Words: 828 Length: 3 Document Type: Essay

Software documentation is an integral part of the software development process. However, the process is often challenging because over the course of a software development project the scope can often change and evolve several times with updates and new builds. Despite the challenges that are presented in effectively documenting the development process, the documentation that is produced can serve as a valuable asset that can be used in future projects

Software Application Process
Words: 1329 Length: 4 Document Type: Research Paper

Software Application Process for a Clinician Provider Order Entry (CPOE) system Software Application Process Clinician Provider Order Entry (CPOE) System The planning, customization, launch and continued use of a Clinician Provider Order Entry (CPOE) system in a local hospital forms the foundation of this analysis. The processes being used prior to the systems' planning and implementation are detailed to provide a basis of comparison of system contribution and performance. A timeline of the

Software Quality Assurance
Words: 589 Length: 2 Document Type: Term Paper

Software Quality Assurance (SQA) is defined as: "A systematic, planned set of actions necessary to provide adequate confidence that the software development process or the maintenance process of a software system product conforms to established functional technical requirements as well as with the managerial requirements of keeping the schedule and operating within budgetary confines." (Galin, cited in Food for Thought, 2005) During the 1970's, companies had difficulty delivering software within the constraints

Sign Up for Unlimited Study Help

Our semester plans gives you unlimited, unrestricted access to our entire library of resources —writing tools, guides, example essays, tutorials, class notes, and more.

Get Started Now