Project Analysis rules:
--- emotional reason (need software to solve the problem)
in two ways:
static analysis Demo:
(1) emotional analysis.
Meet the needs of the business, but also more intuitive, like the way a lot of small and medium enterprises
Figure prototype designer, interactive ----- analyze which features probably do
------ classified ----- ---- ER diagram analysis module functions
(2). rational analysis:
use Case analysis: use case is actually standing in a role to look at the functionality of the system,
what role :( brainstorming) analysis system has
salesperson: standing on the perspective of the salesperson what features should I look at, this is a use Case
customer:
CEOs: statistical analysis system intelligent decision analysis platform
to log a few sales points operating point current number of tickets for each salesperson for each month of the number of tickets
for each flight and now the rest of the total votes cast, real-time updates and
management background:
Administrators relative to the platform operators, this role should have the right to supremacy, it is what can do
a system:
subsystem:
Front Display System (salesperson)
functional back-office systems (CEOs)
management background platform operators main task : analysis of Air flight ticketing system, by using the method of Example idea to build a database table: basic principles: meet the three-Paradigm database 1. atoms of each column of the table can not be divided 2. Do not produce local dependence each table there should be a primary key (a table can only describe a thing) 3. Do not generate transitive dependencies, each column in the table should be directly dependent on the primary key, and not indirectly through other columns dependent on the primary key relationship question the strength of the establishment foreign key relationships build weak ties does not establish a foreign key relationship, but in fact you know that he is a foreign key relationships door to simplify complex issues b. establish the strength of relationship problems
Always like to establish strong relations
tourism
1-m
tourists --- itineraries
visitor route
name from
Id to
Phone length
strong relationship may not be the best choice
cascade table (query, update, delete)
affect the efficiency of database operations
to establish weak relationship:
tourists --- tours
visitor route
name from
Id to
Phone length
does not establish a foreign key relationship, but in fact you know that they are foreign key relationships.
To simplify complex issues.