Your SlideShare is downloading. ×
Sims4 gkce
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Saving this for later?

Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime - even offline.

Text the download link to your phone

Standard text messaging rates apply

Sims4 gkce

571
views

Published on

Design of student information system

Design of student information system


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
571
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
7
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. GKCE-SIM S S tudent I nformation M anagement S ystem
  • 2. SIM S --> U se C ase
  • 3. Sim s Flowchart
  • 4. SIM S --> Class Diagram
  • 5. SIM S - Architecture
  • 6. Layered Architecture Struts Framework Services DAO DB Web Application Services Layer DAO Layer BO Hibernate Business Objects Data Layer
  • 7. Services Layer BaseBusinessService <Interface> BusinessService1 <Interface> BusinessService1 <Interface> BusinessService1 <Interface> BusinessService 1Impl BusinessService 1Impl BusinessService 1Impl * Each Interface will cater to a particular functionality . * Will have base attributes, methods each Service to have.
    • Impl would be the implementation of each service
    • We’ll have a Factory Class to get the Implementation Classes for a particular Service.
    BusinessService Factory Struts Framework Services DAO DB BO Hibernate
  • 8. Business Object Layer (BO) BaseBusinessObject <Interface/Abstract> BusinessObject1 BusinessObject2 BusinessObject3 * Will have base attributes, methods each BO should have.
    • We’ll have a Factory Class to get the Implementation Classes for a particular Service.(Optional, but good to have based on entity)
    • All the BO’s to implement or derive from an interface
    BusinessObject Factory Struts Framework Services DAO DB BO Hibernate
  • 9. Data Access Object (DAO) Layer BaseDAO <Interface/Abstract> DAO1 DAO2 DAO3 * Will have base attributes, methods each BO should have.
    • All the DAO’s to implement or derive from an interface
    • We will have Spring Configure the DAO
    • There would be a DAO for each BO(based on the storage/Data Persistence)
    • DAO would be associated with BO.
    • DAO will have direct JDBC if hibernate is not possible in any scenario.
    • DAO will have basic crud methods.
    Struts Framework Services DAO DB BO Hibernate
  • 10. Package Structure Struts Framework Services BO DAO Layer J2EE component/Package structure Comments
    • Web Project
    • Com.gkce.sims.<module>.actionforms
    • com. gkce.sims.<module>.utils
    • com. gkce.sims.utils
    • will have all JSP and presentation Services/Struts artifacts
    • java Project
    • com. gkce.sims.services
    • com. gkce.sims. services.utils
    • Will have services (interface and their implementation)
    • This could be central component of future services (future projects).
    • java Project
    • com. gkce.sims.bo
    • com. gkce.sims.bo.utils
    • will have all the business objects(only EasyGlass specific).
    • to have a separate domain model for easyGlass
    • java Project
    • com. gkce.sims.dao
    • com. gkce.sims.dao.utils
    • Data Access layer: Hibernate will be part of this.
    • Spring will be part of this; Spring configuration.
  • 11. Thank You Thank You Sreenivas Java Developer IBM