Taking into consideration the RUP you will find four life cycle phases associated with a project- inception, elaboration, construction, and transition. As an OBIEE developer you will be mostly working through the designing, developing, testing, and implementing phase. Sometimes there is involvement to requirements gathering phase but more chances are high to function within the refining the circumstances.You are able 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 study
The execution/development phase: Design and development. At this point is an OBIEE developer I worked by far the most.
The transition/closure phase: Deployment, operations and good health.
The natural Software Development Lifecycle is likewise very similar to this.These are the default Steps in
SDLC:
System Learn
System Model
Software Progress
System Implementation
System Design:
Known clearly as the \"How\" phase, the internal system design determines learn how to implement the system study solutions. This involves:
Output requirements:
Identify the output media, which can include, hard or soft output.
Input requirements:
The output is decided first seeing that it dictates the input requirements.
Determine the input source, for instance, databases, repetitive things by keyboard, mouse or screens (monitors), data screening, voice, data communications, etc.
Storage requirements:
Define the databases.
Records and Sections
System controls and backup:
Determine \"The what could fail 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 software packages.Purchase Considerations:
Customization: Programs you write will meet or exceed design specifications. Gadgets on-the-other-hand needs to be customized to fulfill your specifications.
Extensive customization ought to be avoided loads of reasons. First, it can be costly and time intensive. Second, implementing software package revisions, requires that customization changes be reapplied which in some cases does not retrofit easily.
Re-Engineering: A substitute for customization in that the firm changes it's procedures to comply together with the software package specifications.
Note: The SDLC need to be completed irrespective of write or buy decision.
System Implementation: Test the machine.
Alpha testing so that the system stabilizes.
Beta testing because of the system users.
\"Imagine\" testing from the system analyst.
Populate the databases.
Develop user procedures.
Train the users.
Some approaches for turning-on the system:
Direct: Turn-off the old system and start-up the latest system.
Parallel: Run the historic & new system alongside until the new system was demonstrated to remain reliable. Should really be avoided if there is not sufficient enough users to keep both systems running.
Phased: Parts of the new system are phased in separately.
Pilot: The system is designed by a limited number of users such as a department, or perhaps a district, or perhaps a region, etc.
