I need help answering the following questions:
a. What should be management's role in the system development life cycle (SCLC)?
b. Why does project planning usually come before analysis and design?
c. What are some of the methodologies commonly used for requirements elicitation?
d. How can a prototype be used?
e. What are some metrics that can be used during the SCLC? List the various steps and applicable metrics.
f. What are some reasons why systems fail?
Please see attachment.
1. What should be management's role in the system development life cycle (SCLC)?
It is management's responsibility to ensure that systems thinking are utilized throughout the Systems Development process.
Management complements the SDLC when it comes to Project Quality. It provides a method of managing these unique project efforts, which increases the odds of attaining cost, schedule and quality goals.
The primary benefits of a good Management Process will:
1. Provide consistency of success with regard to Time, Cost, and Quality objectives
2. Ensure customer expectations are met
3. Collect historical information/data for future use
4. Provide a method of thought for ensuring all requirements are addressed through a comprehensive work definition process
5. Reduce Risks associated with the project
6. Minimize scope creep by providing a process for managing changes
Without strong management support, circumstances will affect our ability to satisfy the customer and meet our project and product objectives. Management that is willing to intervene, when asked to, will further increase the probability of successfully delivering a quality product.
2. Why does project planning usually come before analysis and design?
The project management team has a fair idea that whatever be the task at hand, it can be broken down into predictable milestones. Analysis and design are two such milestones. The plan just lays them out as to-dos. Over time as each milestone is reached the plan is reviewed to account for things that the last milestone reveals about the overall needs/progress.
3. What are some of the methodologies commonly used for requirements elicitation?
? Conversational methods: provides a means of verbal communication between two or more people. Methods in this category are also referred to as verbal methods. A typical conversational method is interviews. Other methods include workshop, focus groups, and brainstorming.
? Observational methods: provides a means to develop an understanding of the application domain by observing human activities.
? Analytic methods: Provide ways to explore the existing documentation or knowledge and acquire requirements from a series of deductions.
? Synthetic methods: Forms a coherent whole by systematically combining conversation, observation, and analysis into single methods.
4. How can a prototype be used?
We can use Prototype pattern when a system is independent of how its products are created, composed, and represented.
1). Prototype is based on composition, so it is especially useful when the classes to instantiate are specified at run-time.
2). Prototype can be used to reduce sub classing. When we want to avoid the class hierarchy of factories that parallels the class hierarchy of products, we should use Prototype instead of Factory Method. This is the case when there are many possible product families.
3). When creating a new object is expensive, we can use Prototype to clone an object.
5. What are some metrics that can be used during the SCLC? List the various steps and applicable metrics.
Used comprehensively within IT, formal metrics are needed to reveal the organization's performance including the development of positive and negative trends. This ...
The solution discusses the System Development Life Cycle (SCLC). Items discussed include mangement's role, project planning, prototypes, metrics, and reasons why some systems fail.