rm
Meta Data and Requirements Management & Analysis
What are the assets of a company? Everyone knows the tangible assets like production equipment. Intangible assets are more difficult. Know-how is considered as such an intangible asset. Meta data is high-level description of a business, or business process. You can use it to manage your business more easily. That implies planning and control, as well as adaptation to changing markets or customers.
Extracting Requirements From Existing Data Sources With a Parser
Extracting requirements from existing data sources has 3 aspects:
- The methodology;
- The tools;
- The people.
Migration of Requirements Versus Greenfield
Every now and then a business manager has to ask himself whether to continue with his current processes, or start allover again. So it is appropriate to provide some information on this subject.
Advantages and Disadvantages Of Greenfield and Migration Strategies
Viable questions with this regard are issues like:
- What are we going to do with our current legacy infrastructure?
- What are we going to do with are current legacy technology?
- And what are going to do with our current employees?
Structured Requirements Guidelines
The following general guidelines can help you become successful with your requirements planning projects:
- Aim for approximately 30 externally facing requirements per project for manageability. Treat large projects as several smaller ones.
- Each requirement should have a maximum of 10 or so scenarios for manageability. Break it out into sub-requirements if necessary.
- Each scenario should have at most 10 to 20 discrete steps.
- Estimate 2 to 4 man-weeks of pure development time per scenario in a normal external-facing requirement.
- Assume a 1:1 ratio of development time to test time.
Business Case Requirements Management
Did you ever realized how many projects fail, and how this occurs?
Forrester reports on poor requirements (2006) a survey of the Standish Group's 1994 Chaos Report. Standish found, querying over 352 companies reporting on over 8,000 software projects, that the top three project impairment factors were:
- Lack of user input (12.8% of respondents);
- Incomplete requirements and specifications (12.3%);
- Changing requirements and specifications (11.8).
Implementation Services For Business Requirements Management: Consultancy and training
We help you deliver results by successful implementation based on extensive experience gained through many projects. We prefer fixed price fixed date programs, as they offer you and us the utmost value.
Prerequisites For a Successful Application Of Business Requirements Management
The quality of business software requirements is a limiting factor on the success of software development projects.
Commonly Used Business Requirements Planning Methodology and Approach (and how to improve it)
Currently, business managers leave the process of gathering of business requirements management specifications often to the 'experts'. We do not recommend this, because because requirements management is a serious part of business planning, and therefore should be handled by business management. Common behavior:
- ICT experts run the project, and all is in their 'safe hands'.
- The match between business and delivered project results is to be established during the project test phase. And thus much too late, and too expensive.
Requirements For a Green ICT
Submitted by Hans Lodder on Thu, 03/07/2008 - 14:42Greenfield Is the Best Solution To Implement a New Idea!
Submitted by Hans Lodder on Thu, 29/05/2008 - 07:06If you want to implement a new idea it is the best solution to start with a greenfield. It is an easy solution, no problems with history or legacy systems, and no difficult questions about how you got stuck with all those problems. And talking about history is boring too. Greenfield has only advantages! Or?
