Taking into consideration the RUP you can find four life cycle phases of the project- inception, elaboration, construction, and transition. As an OBIEE developer you will be mostly working during the designing, developing, testing, and implementing phase. Sometimes there is involvement to requirements gathering phase but more i'll bet to operate in the whole refining the necessities.You can define the OBIEE project Life cycle as below:
The initiation/inception phase: Creating business case, Project planning and feasibility study.
The elaboration/planning phase: Resource Planning, Requirements gathering and study
The execution/development phase: Design and development. It is here that as a possible OBIEE developer I worked by far the most.
The transition/closure phase: Deployment, operations and care.
The conventional Software Development Lifecycle is likewise connatural this.These would be the default
Steps in SDLC:
System Learn
System Design
Software Development
System Implementation
System Design:
Known because the \"How\" phase, sst design determines how to implement the system study solutions. This involves:
Output requirements:
Find the output media, which include, hard or soft output.
Input requirements:
The output is determined first given it dictates the input requirements.
Affect the input source, which can include, databases, repetitive things by keyboard, mouse or screens (monitors), data screening, voice, data communications, etc.
Storage requirements:
Define the databases.
Records and Professions
System controls and backup:
Determine \"The what should go awry scenarios\".
Unauthorized access, determine security measures for software & hardware.
Lost or corrupted databases (bank vaults of information), determine on-site backup.
Disasters, determine off-site database storage, computer processing and communication network back-ups (AT&T, MCI & Sprint). Develop system specifications for your programmers.
Software Development:Build software programs as per design sepcifications.
Make or by decision.
Write the programs in-house or purchase tools and equipment.Purchase Considerations:
Customization: Programs you write will meet or exceed design specifications. Software packages on-the-other-hand must be customized to satisfy your specifications.
Extensive customization should be avoided loads of reasons. First, it truly is costly and time-consuming. Second, implementing software package revisions, requires that customization changes be reapplied which many times doesn't retrofit easily.
Re-Engineering: An alternative to customization for the reason that the firm changes it's procedures to comply in the software package specifications.
Note: The SDLC needs to be completed regardless of the write or buy decision.
System Implementation: Test sst.
Alpha testing till the system stabilizes.
Beta testing via the system users.
\"Just imagine that\" testing because of the system analyst.
Populate the databases.
Develop user procedures.
Train the users.
Some approaches for turning-on the machine:
Direct: Turn-off the historic system and start-up the new system.
Parallel: Run the historic & new system next to each other before new system has demonstrated to remain reliable. Ought to be avoided if there is not enough users to keep both systems running.
Phased: Parts of the latest system are phased in separately.
Pilot: The internal system is used by the limited number of users like a department, or possibly a district, or perhaps a region, etc.
