DOC PREVIEW
K-State CIS 764 - Design process and artifacts

This preview shows page 1-2-3-27-28-29 out of 29 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

CIS 764 Database Systems EngineeringSlide 2Slide 3Slide 4Slide 5Slide 6Slide 7Slide 8Slide 9Slide 10Slide 11Slide 12Slide 13Slide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Slide 23Slide 24Slide 25Slide 26Slide 27Slide 28Slide 29Fall 2007 http://www.cis.ksu.edu1CIS 764 Database Systems Engineering L4: Design process and artifacts (and reverse engineering)Fall 2007 http://www.cis.ksu.edu2CIS 764 Database Systems Engineering  No new homework assignment today.Fall 2007 http://www.cis.ksu.edu3CIS 764 Database Systems Engineering technology …. J2EE, dotNet, Ruby, … JDev, Eclipse, VisStudio, .. methodology … RUP (Rational Unified Process), MDD / MDA (model driven development / architecture) extreme programming / developent management … install tools, backups, product selection, training, process / people management, security policies, schedules, budget, …Fall 2007 http://www.cis.ksu.edu4CIS 764 Database Systems Engineering Note: Traditional DB design - -> data models:> ER diagrams (P. Chen) ………………………….conceptual , not OO> schema diagrams (Access, Visio, other tools) ... tables, not OO> UML (an emerging notation for data models) … UML, not OO !! read: www.agiledata.org/essays/umlDataModelingProfile.html Scott Ambler’s own profile for UML database models.Fall 2007 http://www.cis.ksu.edu5CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu6CIS 764 Database Systems Engineering… notes: stereotype is “data model” storage map is “relational database” kinds of classes: entity lookup table index stored procedure association table view kinds of associations: “arrow” aggregation composition column tags: PK, FK, …Fall 2007 http://www.cis.ksu.edu7CIS 764 Database Systems Engineering conceptual model … most abstract, language/platform independent (never a table model ) logical model …….. specific parameters, constraints physical model …. tables, concrete typesFall 2007 http://www.cis.ksu.edu8CIS 764 Database Systems Engineering OO design process: … in practice, always iterativeuse case model (requirements) … what operationsProcess model (“swim lanes”) … coordination of opsGUI design: page designs, page flow, mock-up prototype, state models domain model use case assertions, class modelSemantic constraints: invariants, operation assertions, state modelsphysical data model (and OO to relational mapping)Fall 2007 http://www.cis.ksu.edu9CIS 764 Database Systems EngineeringUML tutorials: OMG (Object Modeling Group) http://www.uml.org/ Rational / Borland (old, but simple) http://dn.codegear.com/article/31863Fall 2007 http://www.cis.ksu.edu10CIS 764 Database Systems Engineering Sample documents from Sundeep MSE: A User Community (based on Orkut.com)  not a perfect example … several weak features.Fall 2007 http://www.cis.ksu.edu11CIS 764 Database Systems EngineeringAdd FriendCreateManage PhotosManage ProfileManage FriendsManage CommunitiesuserDelete FriendScrap FriendManage Profile PhotoManage Album PhotosDeletePost MessageJoinFall 2007 http://www.cis.ksu.edu12CIS 764 Database Systems Engineering Manage Friends * Purpose: The purpose of this part of the application is to enable user to manage his friends list. *Input: The user will select his friends section and choose to manage friends with various options given. *Processing: The user selection will be validated and accordingly the action is being performed again the user’s account at the server. Friends list is then being processed at the server. *Output: The required action is being performed based on the selection of the action, between Add friend, Delete friend, Scrap friend.Fall 2007 http://www.cis.ksu.edu13CIS 764 Database Systems Engineering Process model: <did not have one !!!> That means any user can do any (legal) operation in any order. whereas, typical enterprise has coordination of operations: e.g. I cannot access KATS until I am appointed as faculty.Fall 2007 http://www.cis.ksu.edu14CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu15CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu16CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu17CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu18CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu19CIS 764 Database Systems Engineering--Invariants--Every photo in database should be associated to a single user. Owner is a member of the community. --Every photo in database should be associated to a single user. association photoasso between Photo[0..*] role userphoto SocialUser[1] role user end --Owner is a member of the community. context SocialUser inv CommOwnerIsMember: SocialUser.allinstances -> forAll(S | S.myCommunities.Owns->includes(S) implies S.myCommunities.member->includes(S))Fall 2007 http://www.cis.ksu.edu20CIS 764 Database Systems EngineeringCreateCommunity(c_name : String, c_pic : String) : Booleanpre : Community.allInstances.c_name->excludes(c_name)post : Community.allInstances.c_name=Community.allInstances.c_name@pre->including(c_name)post : Community.allInstances.c_pic=Community.allInstances.c_pic@pre->including(c_pic)DeleteCommunity(c_id : Integer)pre : Community.allInstances.c_id->includes(c_id)post : Community.allInstances.c_id=Community.allInstances.c_id@pre->excluding(c_id)post : Community.allInstances.c_name=Community.allInstances.c_name@pre->excludes(c_name)post : Community.allInstances.c_pic=Community.allInstances.c_pic@pre->excludes(c_pic)Fall 2007 http://www.cis.ksu.edu21CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu22CIS 764 Database Systems Engineering Test Plan: derived from method assertions include plan for function and regression testing function: test both positive action and invalid inputs & states regression: JUnit , NUnit … repeat tests as system is changed Registering a Social UserLoginAdding a FriendDeleting a FriendScrap a FriendCreating a CommunityJoining a CommunityManage photos of userFall 2007 http://www.cis.ksu.edu23CIS 764 Database Systems EngineeringFall 2007 http://www.cis.ksu.edu24CIS 764 Database Systems EngineeringNow the reverse engineering process:Fall 2007 http://www.cis.ksu.edu25CIS 764 Database Systems


View Full Document

K-State CIS 764 - Design process and artifacts

Documents in this Course
Load more
Download Design process and artifacts
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Design process and artifacts and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Design process and artifacts 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?