2.3 User Classes and Characteristics
There are 3 classes in developing system: Orders, Clients, Films.
Orders is main class in our system, because it give all needed details about films, clients and charges. For example, user can get to know what client take what film, and when he should return it. Thanks to it system will work without any mistakes. If client wants to get film that is temporarily absent in storehouse, system will generate appropriate message.
Clients is a class which give a full information about client such as name, surname, Id, address, phone. So different clients will never be mixed in tables and they can be initialized by all these characteristics.
Films are class with information about all films, that are categorize by genre, actors, duration, status. Such method of organization data is irreplaceable according to all variety of films that are released today. There is no constraints for users with different expectations, backgrounds, and experience.
2.4 Operating Environment
The accounting system doesn’t consume many operating system so it will work on any operating systems such as Windows 7, Vista ,XP or any other computers. Also every computer will be able
to handle it properly. So some specific hardware platform isn’t needed.
2.5 Design and Implementation Constraints
More and more actions will be foreseen in our system, according to plan of developing this system. This product will be useful to any rental center that take care of their employees, which saves time by automating the process of accounting films and process their orders.
2.6 User Documentation
To our project will be added all tutorials how to use database, how to create query, how to use interfaces.
1.System Features
1.1System Feature 1
Accounting system will be provided by JDBC environment. There is a J2SE Development Kit 5.0 (JDK 5.0) to implement main programming code. Then we should have realization all tables in database. The most suitable for our project is MySQL , an open source database. We can download it from MySQL Official Site.
3.1.1 Description and Priority
The highest priority is authorization system and database organization. Due to the structured data, all information and connections between attributes should be clearly built. So any query would work correctly.
3.1.2 Stimulus/Response Sequences
The sequences of user acts:
Entry to the system;
Filling in the personal information about clients and enlisting them to client’s database;
Taking payment and create new order;
Execute documentation about current situation of films storage;
Execute documentation about current situation of borrowed films;
Execute documentation about current situation of payments (bond and loans);
Exit system.
3.1.3 Functional Requirements
To provide all these query or to have access to system we can use the basic two scenarios access to the database - from applets downloaded over the network and stand-alone applications running on the client. The most common area of application Java - is the creation of applets loaded over the network to the client machine as part of a web- document ( in most cases, html). As in any other field of application programs , a large proportion of these applets should be able to interact with the database and to a database located on a server (not on the client machine , since the applet has a more significant restrictions on access to the resources of the machine compared with the application ) .
Java architecture allows you to create standalone applications. Of course, they, like applets, run the virtual machine, but unlike the applets downloaded over the network exist outside the context of web-documents. In this case, the scenario differs and restrictions on access to local resources are removed to the level of access to them through a virtual machine.
Picture 1.
System Feature 2 (and so on)
2.External Interface Requirements
2.1User Interfaces
The user interface is not available at this stage.