System Analysis
Use Case Model
This diagram describes HOW the system is used, and by WHOM. As you can see, the Student is able to create a new account, view his/her own account information, update that account information, and delete the account. An Administrator has the ability to view all the Student accounts, and additionally can also delete an account.
Domain Model
This diagram describes the various concepts that make up our domain. We have the System, which is essentially a collection of zero or more Users. A User could be a Student or an Administrator. If the User is a Student, then there are additional attributes associated with him/her, such as Student Number and Possible Contribution. We also see that the System is capable of adding, updating, deleting, and retrieving Students.
Why is this important?
These diagrams, along with the conceptual/physical data model diagrams and our screen mock-ups, will go into our System Design Document. Remember, if we want to get an A in this project, we will have to show as much documentation and structure as possible.
Leong, please go ahead and make the conceptual/physical data model diagrams. If we get all of our analysis/design work done this week, we will be in good shape to begin implementation next week. Thanks.
Comment by MI — January 30, 2008 @ 5:25 pm
Gene, we can use Function Point analysis against the Use Case Model to create an estimate for the technical deliverable.
Comment by MI — January 30, 2008 @ 5:32 pm
Hi,
Is it okay for a student to delete the account without a permission?
If that is done, is there a tool to record a deleted account (back-end)?
Comment by oge — January 31, 2008 @ 3:09 pm
In terms of security, I believe it was Leong that mentioned that also:
At what point are the policies laid down to be followed for say the access control, identification etc.
Comment by oge — January 31, 2008 @ 3:12 pm
So Leong if the user is administrator, the username and email address is all that are required to login, would that be enough in terms of access control?
Comment by oge — January 31, 2008 @ 3:13 pm
Good questions, Oge! I think the requirements about access control and auditing (recording deletions) need to be clarified with the stakeholders. We could add a lot of bells and whistles to this, but we need to make sure that we don’t get out of scope. As far as usernames and passwords for logging in, I agree that we need to have them, but they are typically not represented on a conceptual model diagram. They will be represented in Leong’s ERDs, though.
Comment by MI — January 31, 2008 @ 4:20 pm
Mohammad, I have done developed the conceptual ERD and logical ERD, I will try to post it to this blog, or at least send it to your BU email for your review.
Thanks,
Leong.
Comment by Leong — January 31, 2008 @ 4:30 pm
I think that within the scope of this project an email and user name are enough, however, I think an Email and password would make more sense. What do you think?
Comment by admin — January 31, 2008 @ 10:59 pm