Considering the RUP you will find four life cycle phases associated with a project- inception, elaboration, construction, and transition. As a possible OBIEE developer you'll be mostly working while in the designing, developing, testing, and implementing phase. Sometimes there is involvement in requirements gathering phase but more chances are to operate inside the refining the circumstances.It's possible to 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 analysis
The execution/development stage: Design and development. At this point since a OBIEE developer I worked the most.
The transition/closure phase: Deployment, operations and good health.
The healthy Software Development Lifecycle can be identical to this.These would be the default Steps in
SDLC:
System Study
System Design
Software Development
System Implementation
System Design:
Known as the \"How\" phase, the machine design determines how you can implement the system study solutions. This involves:
Output requirements:
Determine the output media, for instance, hard or soft output.
Input requirements:
The output is decided first given that dictates the input requirements.
Identify the input source, which include, databases, repetitive things by keyboard, mouse or screens (monitors), data screening, voice, data communications, etc.
Storage requirements:
Define the databases.
Records and Paddies
System controls and backup:
Determine \"The what could go awry scenarios\".
Unauthorized access, determine security measures for software & hardware.
Lost or corrupted databases (bank vaults of real info), determine on-site backup.
Disasters, determine off-site database storage, computer processing and communication network back-ups (AT&T, MCI & Sprint). Develop system specifications regarding the programmers.
Software Development:Build software programs according to design sepcifications.
Make or by decision.
Write the programs in-house or purchase gadgets. Purchase Considerations:
Customization: Programs you write will meet or exceed design specifications. Gadgets on-the-other-hand have to be customized to fulfill your specifications.
Extensive customization should be avoided for 2 reasons. First, it really is costly and time consuming. Second, implementing software package revisions, requires that customization changes be reapplied which quite often doesn't retrofit easily.
Re-Engineering: An alternative to customization for the reason that the company changes it's procedures to comply when using the software package specifications.
Note: The SDLC have to be completed regardless of the write or buy decision.
System Implementation:Test sst.
Alpha testing before system stabilizes.
Beta testing from the system users.
\"What if\" 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 original system and start-up fresh system.
Parallel: Run the historic & new system alongside till the new system has shown to become reliable. Should be avoided when there is insufficient users to keep both systems running.
Phased: Parts of the new system are phased in separately.
Pilot: The machine is utilized by the limited number of users such as a department, or a district, or maybe a region, etc.
