Start 9.00 a.m.
_________________________________________________________
OK, so my main objective today is to figure out what tasks i need to do for the design, and how long these might take. Also this morning i put together a time table so i can improve my time management, or at least try to. :D
Below is what i specified in my milestones.
18th April - Design Goals
- Interface design (Template for website, Form for mapping and jobs, Print out design, Other appropriate form designs)
- UML diagram (Basic)
- Database (Conceptual design, Logical design, Physical design)
Break down of tasks
I am going to do the design stage the best way that is easy for me. This is why i am going to sort of mix up the interface design with the database design, and based on this i will come up with the classes i need for the UML diagrams and work from there. This is mainly because i think in database sort of terms, with entities, attributes and relationships, as this makes it easier for me to see the whole picture.
Interface (7 days)
- Come up with a list of tasks the users will need to acomplish by using this system. This way i can get a better idea of what the user needs to do, and what data they need to input/use.
- Make a list of data needed (most likely start the database design cause i'm naughty!).
- Design the template layout. I will need to come up with some pretty but practical look for the site.
- Figure out, based on the data etc needed, what forms i will need for input and output.
- Make the designs on the computer, so i have a more procise design to upload/show people.
Database (2 days)
- Create entities, attributes, relationships, primary keys (PK) and foreign keys (FK).
- Produce a logical entity relationship diagram (ERD).
- Produce a data dictionary.
- Produce a physical diagram with all of the data types.
- Have these diagrams in visio.
UML (Unified Modelling Language) (6 days)
- Create a basic starting design with entities, attributes and relationships.
- Based on what i came up with in the design of the forms, make a list of functionality that the program will need to perform.
- Make a list of all the functionality and prioritise all of these. This way if i get behind i will only implement the most important functionality.
- Once i have an idea of the whole program, i will produce the final UML diagram.
************************************************************************
Break 11.30 a.m. - 12.00 p.m.
************************************************************************
My plan for the rest of the day is to start the list of tasks needed to perform in the system. If i get this done i will move onto the template design.
Tasks - so far
Users
- Add
- Edit
- Delete
- View - list of jobs
- Assign jobs
- Assign permissions
Clients
- Add - one or more locations
- Edit
- Delete
- View
- View location on map
Jobs
- Add
- Edit
- Delete
- Assign job to user
- View
- Sort view
- Assign the job as completed
Maps
- Choose which jobs will be mapped out, add prioritys if needed.
- Get directions once jobs are selected/prioritised.
- View directions.
- Print directions. (Select what to print).
Data needed
Below is the basic un-normalised data that i need. Information about the staff or users of the system, the jobs that need to be done and the clients information.
Staff ID of some type
User name, first & last
Password?
Job #
Job description
Job completed
Client #
Client name
Client phone number
Location Address
Location geocode
Break 3.30 p.m. - 5.30 p.m.
************************************************************************
Carry on with design on paper.
_________________________________________________________
Finish 8.00 p.m. - 8 hours.
_________________________________________________________
No comments:
Post a Comment