Considering the RUP you can find four life cycle phases associated with a project- inception, elaboration, construction, and transition. Since a OBIEE developer you'll be mostly working in the course of the designing, developing, testing, and implementing phase. Sometimes there is involvement in requirements gathering phase but more chances are to operate in the whole 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 phase: Design and development. This is when is an OBIEE developer I worked essentially the most.
The transition/closure phase: Deployment, operations and maintenance.
The normal Software Development Lifecycle is likewise identical to this.These are the default Steps in
SDLC:
System Learn
System Plan
Software Formation
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:
Affect the output media, such as, hard or soft output.
Input requirements:
The output is set first seeing that it dictates the input requirements.
Find 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 Professions
System controls and backup:
Determine \"The what can go wrong scenarios\".
Unauthorized access, determine security measures for software & hardware.
Lost or corrupted databases (bank vaults jumble), 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 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. Tools on-the-other-hand need to be customized to match your specifications.
Extensive customization ought to be avoided for a couple of reasons. First, it can be costly and time consuming. Second, implementing software package revisions, requires that customization changes be reapplied which in some cases doesn't retrofit easily.
Re-Engineering: An alternative choice to customization as this company changes it's procedures to comply together with the software package specifications.
Note: The SDLC must be completed no matter what the write or buy decision.
System Implementation: Test sst.
Alpha testing till the system stabilizes.
Beta testing from the system users.
\"Lets say\" testing by 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 next to each other until the new system was demonstrated to be reliable. Should really be avoided if not sufficient enough users to keep both systems running.
Phased: Aspects of the new system are phased in separately.
Pilot: The internal system is used by the limited number of users as a department, or possibly a district, or a region, etc.
