PROJECT SECME

1
PROJECT SECME
UCF
Software Engineering Fall 2002 Dr. Damla
Turguts Students

• Carthik A. Sharma
• Juan Carlos Vivanco
• Majid Khan
• Santhosh Kumar Grandai.
• http//www.geocities.com/secmep/

2
Overview

• High Level Design
• - Architectural Design
• - Design Issues
• Detailed Design
• - Resolution of Issues
• - Class Diagrams
• - ER Model

3
High Level Design

• Architecture
• Design Issues

4
Architecture
5
Architecture

• Client interacts through http
• Presentation Layer
• Business Layer
• Service Components
• Database
• Tomcat 4.0 hosts all pages, components

6
Presentation Layer

• Java Server Pages
• Content Generation
• User Interface
• Uses Business Layer to modify/retrieve data

7
Business Layer.

• Java beans
• Business related functionality
• Uses service components

8
Service Components Database

• Connection Manager
• access to the database
• - Email Component
• sends email via SMTP
• Database
• MS Access

9
Design Issues

• Reusability
• Maintainability
• Testability
• Performance
• Portability
• Safety
• Security

10
Design Issues

• Technical Difficulties expected,
• - Integration of Modules
• - Installing the system
• - Increase in Degree of Complexity
• Solution
• - Integration to be done in presence of
  team member responsible for developing that
  module
• - Take more time in Installation
• - Requirements on priority basis

11
Design Issues

• Design Tradeoff
• - Use of .ASP ( lack of knowledge)
• One team member well versed in Java
• - Availability of development tools
• Tomcat 4.0 free
• MS Access Universally available at SEECS

12
Why this architecture?

• Overall architecture similar to common web-based
  applications.
• Service components used by other modules
• and so shown separately
• Lucidity in conceptualization.

13
Design Issues 1

• Modification of Information
• Modify defined as deletion and addition of
  record
• Difficult to modify just one parameter for a
  student
• Simplifies implementation

14
Design Issues 2

• Accessing the database and messaging
• Several modules need access to database
• The To and From addresses need to be
  dynamically specified for email
• Separate structural module Service Components

15
Design Issues 3

• Adding Event Details
• Events mapped to the rest of data
• New event specified each time modification
  occurs
• Preserve historic data (invisible)

16
Design Issues 4

• Data Organization
• Different classes and tables for different
  abstract types, such as event, student and
  organization.
• Modularity of data, code.

17
DATABASE CONCEPTUAL SCHEMA
18
Class diagram
19
Requirements satisfied

• Most requirements are satisfied by design
• Rest are to be implemented, such as
• user friendliness
• data formatting of the web pages
• as part of the implementation phase.

20
PROJECT SECME
UCF
Software Engineering Fall 2002 Dr. Damla
Turguts Students
Thank You! ? Questions? ?

• Carthik A. Sharma
• Juan Carlos Vivanco
• Majid Khan
• Santhosh Kumar Grandai.
• http//www.geocities.com/secmep/