How UML and Agile Development fit together Essay

How UML and Agile Development fit together - Essay Example 2. How can software affect both product development and product management? In the current competitive environment, development of products that win the appeal of the customer is very important for success in the market. On the other hand, the success of any product is dependent upon the skills and competencies of the product manager; the latter is responsible for development of products. The product development and management process includes processes such as product requirement definition, release definition, and product life cycles. However, product development and management is complex and includes numerous stakeholders, responsibilities and processes. This means that contemporary product managers have to be heavily assisted by technology, including appropriate software (Gorchels 23). There is need for the right kind and combination of software to be applied for the desired product to be achieved. 3. List and explain the common tasks performed during software architecture. Some of the common tasks performed during software architecture include; Proposal development: A software architect develops proposals for new software based on new product needs or customer requirements. Design: This involves the design and creation of new software on the basis of proposals made. Software realization: This involves supervision of the whole process of software development from design through creation up to the point that the software is ready to be launched. Software validation: A software architect plays the role of validating software for a company especially when such software has been outsourced or is new. This involves ascertaining the effectiveness of the software and ensuring it is fit for purpose. Report writing: The software architect is charged with producing periodic reports during the course of software development. 4. What are the common inputs, constraints, and outputs found during architectural problem solving? Software design inputs are very helpful towar ds formalization of architecture requirements and constraints. Some of the common inputs in software design include use cases, usage scenarios, functional requirements, non-functional requirements, and technological requirements (Clements et al. 72). Some common constraints in software design include poor technology, fast changing scenarios and unanticipated functional or non-functional requirements. 5. Why is it important for software architects to be familiar with the discipline of requirement engineering? Requirements engineering is mainly concerned with the identification and communication of the purpose of a software-intensive system, and contents in which it will be used. Basically it acts as the bridge between the need of software users, customers, and other groups affected by a software system, and opportunities and capabilities provided by software (Malan and Bredemeyer 1). It is important for software architects to be familiar with requirements engineering because it provi des them with the opportunity to understand how to bridge the gap between what users need and system design to meet those needs. 6. What are the four main activities performed during requirement engineering? Explain. The following activities are performed during requirement engineering: Requirements discovery: Involves Requirements analysis: this involves