Web Demonstration for BizRules - PowerPoint PPT Presentation

1 / 19
About This Presentation
Title:

Web Demonstration for BizRules

Description:

Windows series or any other Java enabled OS. Project Background. Context Diagram. Process ... Mentor Meeting. Feedback. SRS (Software Requirements ... – PowerPoint PPT presentation

Number of Views:14
Avg rating:3.0/5.0
Slides: 20
Provided by: jBa85
Category:

less

Transcript and Presenter's Notes

Title: Web Demonstration for BizRules


1
Web Demonstration for BizRules
  • Jeong Wook Bang

2
Outline
  • Introduction
  • Project Background
  • Process
  • Requirements
  • Analysis
  • Design
  • Reflection
  • Lesson Learned
  • Questions

3
Introduction
  • Jeong Wook Bang
  • MSIT-SE
  • Client
  • NEO, MSE studio team
  • Mentor
  • Mel Rosso-Llopart
  • Technical Advisor
  • Chankyu, Park

4
Project Background
  • BizRules
  • Rule Based Management Systems
  • Web Demonstration for BizRules
  • Business Assistant
  • Customer Credit Evaluation System
  • Code Generator
  • Generate code templates to invoke rules in EJB
    beans or KnowledgeBase

5
Project Background
  • Web Demonstration for BizRules
  • Be integrated to BizRules of NEO team.
  • Database MySQL
  • Middleware J2EE
  • Windows series or any other Java enabled OS

6
Project Background
  • Context Diagram

7
Process
  • General process is not suitable for Practicum
  • Defining the process for practicum
  • In the Software Process Definition Course
  • Consists of five phases

8
Process
  • Life Cycle

9
Requirements Engineering
  • Elicitation
  • Uncovers unrefined user requirements
  • Analysis
  • Uncovers potential problems
  • Specifications
  • Represent analyzed requirements
  • Validation
  • Ensures that the requirements are correct and
    unambiguous
  • Maintenance
  • The requirements become basis

10
Requirements
  • Requirements Engineering

11
Requirements
  • Client Meeting
  • Requirements prioritization
  • Mentor Meeting
  • Feedback
  • SRS (Software Requirements Specifications)
  • 12 Requirements
  • Written for 8 weeks
  • To be atomic and testable

12
Analysis
  • Architecture

13
Analysis
  • Quality Attributes

14
Design
  • Use case Diagram

15
Design
  • Use case Diagram

16
Design
  • User Interface

17
Reflection
18
Lesson Learned
  • Satisfying the client is not easy
  • Abstracting requirements is very hard

19
Questions
  • How can I do if schedule slip happens seriously?
  • Low quality or quantity?
Write a Comment
User Comments (0)
About PowerShow.com