Week 6 Use Case Diagram

This week we were learning use case modeling. It is an objected-oritented approach to model user requirements. The former diagram is a use case diagram created to illustrarte the behavior of shoes stock management system.
If we have drawn an enent table, it is easy to draw a use case diagram. But system analysists have to pretend that it is difficult to draw it. The users are going to pay money. We must prove our work is hard and valuable.
VP is a very useful tool to draw diagram. But it is complex for beginner to use it. I have never seen some of the functions it provides.

week 5 traditional approach and developing event table

In week 5, we were talking about SDLC in traditional approach. The data flow diagram is vital in the traditional approach. But it seems that system analysts do not like it. The main reason is DFD view the business process as a set and mechanistic hierarchy. Today, more and more business are becoming dynamic so that DFD can not define all business well.

I have tried to draw an level-0 DFD for an online sales system.

I also discussed event tables with my classmates. I found that most people were trying to add lots of events into the event table. Somebody's event table has more than 40 rows! I think it is good to view a system from different angles. But they are too ambicious. We are beginners and we are going to draw user case diagram and write user case narratives. It is just too complex if we add every thing into one system. Thus, I modified my event table and followed "CRUD". It is a very logic way to include all important events although it is not very flexiable.

week 4 mock interview and event table

In week4 , we had an interview with tutor. An draft event table is drawn here, the red words are unsure part of the event table, I am trying to improve the quality of event table.