Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
By
Course Instructor: Mr. Teshome Megersa Computer Science & IT Department Arba Minch University, Arba Minch, Ethiopia
Acknowledgement
Prior to all we would like to give honorable thanks to God to help and give us strength throughout the progression or completion of this project and enabling us to finish it peacefully. We extend our deepest gratitude to our instructor/advisor/ Mr.Teshome Megersa to initiate us to do this project and for his excellence advice staring from the inception to construction of this project. We would also like to express hear full thanks to Amibara Agriculture Development plc. Employees for their great contribution to give us information and encouragement go beyond the accomplishment of this project. Finally we would like to thank our fiends for they share us information and have contributed greatly and our family for they support us financially to finish this project.
ii
Table of Content
Content --------------------------------------------------------------------------------------------------Page Chapter One 1.1 Introduction---------------------------------------------------------------------------------------------1 1.2 Background of the project ---------------------------------------------------------------------------1 1.3 Statement of the Problem ----------------------------------------------------------------------------1 1.4 Objectives------------------------------------------------------------------------------------------------2 1.4.1 General Objective----------------------------------------------------------------------------------2 1.4.2 Specific Objective----------------------------------------------------------------------------------2 1.5 Feasibility Study ---------------------------------------------------------------------------------------3 1.5.1 1.5.2 1.5.3 1.5.4 Operational Feasibility---------------------------------------------------------------------------3 Technical Feasibility------------------------------------------------------------------------------3 Economic Feasibility------------------------------------------------------------------------------3 Schedule Feasibility-------------------------------------------------------------------------------4
1.6 Scope of the Project -----------------------------------------------------------------------------------6 1.7 Significance of the Project ---------------------------------------------------------------------------7 1.8 Target Beneficiaries of the System -----------------------------------------------------------------7 1.9 Methodology --------------------------------------------------------------------------------------------7 1.10 Data Source -----------------------------------------------------------------------------------------7 1.10.1 1.11 1.12 1.13 1.14 1.15 1.16 Fact Finding Techniques-------------------------------------------------------------------------8 Systems Analysis and Design--------------------------------------------------------------------8 Development Tools--------------------------------------------------------------------------------8 Testing procedures (types of testing used)----------------------------------------------------9 Limitation of the project------------------------------------------------------------------------10 Risks and contingencies-------------------------------------------------------------------------10 Assumptions and Constraints------------------------------------------------------------------10
iii
Chapter Two 2.0 Introduction to the Existing System---------------------------------------------------------------11 2.1 Players in the existing system-----------------------------------------------------------------------11 2.2 Business rules------------------------------------------------------------------------------------------12 2.3 Registration procedure:-----------------------------------------------------------------------------12 2.4 Major functions/activities in the existing system-----------------------------------------------12 2.5 Report generated in the existing system---------------------------------------------------------13 2.6 Forms and other documents of the existing systems------------------------------------------13 2.7 Bottlenecks (problems) of the existing system--------------------------------------------------16 2.8 Practice to be preserved-----------------------------------------------------------------------------19 2.9 Proposed solution to address problems of the existing system-------------------------------20 2.10 Requirements of the Proposed System-------------------------------------------------------20
3.0 Modeling of Proposed System----------------------------------------------------------------------23 3.1 Use Case of Proposed System----------------------------------------------------------------------24 3.2 Sequence Diagram-----------------------------------------------------------------------------------32 3.3 Activity Diagram-------------------------------------------------------------------------------------40 3.4 Analysis Level Class Diagram---------------------------------------------------------------------41 3.5 User Interface Prototyping-------------------------------------------------------------------------43
iv
Chapter Four System Design 4.0 Class Type Architecture --------------------------------------------------------------------------44 4.1 Component Modeling------------------------------------------------------------------------------47 4.2 Deployment Modeling-----------------------------------------------------------------------------48 4.3 Persistence Modeling------------------------------------------------------------------------------49 4.4 User Interface Designing--------------------------------------------------------------------------51 Chapter Five Implementation and Testing 5. Implementation and Testing-----------------------------------------------------------------------59
Chapter Six Conclusion and Recommendation 6.0 Conclusion and Recommendation---------------------------------------------------------------71 6.1 Conclusion--------------------------------------------------------------------------------------------71 6.2 Recommendation------------------------------------------------------------------------------------71 6.3 References------------------------------------------------------------------------------------- -------72
List of Figures Fig 1 Credit sales invoice -------------------------------------------------------------------------14 Fig 1.1 Cash sales invoice-------------------------------------------------------------------------15 Fig 2 Use Case Diagram the of Propose System----------------------------------------------25 Fig 3 Manager Login Sequence Diagram-----------------------------------------------------33 Fig 3.1 Store keeper Login Sequence Diagram----------------------------------------------34 Fig 3.2 New Product Registration Sequence Diagram-------------------------------------35 Fig 3.3 Product Request Sequence Diagram ------------------------------------------------37 Fig 3.4 Sequence Diagram for Searching Product-------------------------------------------38 Fig 3.5 Sequence Diagram for Report generating ------------------------------------------39 Fig 4.Activity Diagram ---------------------------------------------------------------------------40 Fig 5 Conceptual Class Level Diagram -------------------------------------------------------42 Fig 6 User Interface Prototyping---------------------------------------------------------------43 Fig 7 Class Type Architecture-------------------------------------------------------------------45 Fig 8 Component Modeling----------------------------------------------------------------------48
vi
Fig 11 Login Screen ---------------------------------------------------------------------------------51 Fig 11.1 Stock Market Management System Main Menu Page------------------------------52 Fig 11.2 Account Creating Page--------------------------------------------------------------------53 Fig 11.3 Document Viewing Page------------------------------------------------------------------54 Fig11.4 New Product Registering Page-----------------------------------------------------------55 Fig11.5 Product Requesting Page------------------------------------------------------------------56 Fig11.6 Product Distributing Page-----------------------------------------------------------------57 Fig11.7 Product Searching Page-------------------------------------------------------------------58
vii
Table: 2 Schedule Feasibility------------------------------------------------------------------------4 Table: 3 Cost Benefit Analyses---------------------------------------------------------------------5 Table: 4 Cost of the project-------------------------------------------------------------------------6 Table: 5 Fact Finding Techniques-----------------------------------------------------------------8 Table: 6 Description of each Class Type Architect--------------------------------------------46
Table: 7 Test Cases 1 Customer Registration -----------------------------------------------61 Table: 7 .1Test Case 2 Login --------------------------------------------------------------------63
viii
Abbreviations
UI: User Interface UML: Unified Modeling Language HTML: Hypertext Markup Language API: Application Programming Interface SMMS: Stock Market Management System OS: Operating System O/R: Object/Relational XAMPP: X ->to be read as "cross", meaning cross-platform) A->Apache HTTP Server M ->MySQL P->PHP P->Perl
ix
Abstract
This project is designed to create stock market management system for Ethiopian agricultural products. In this project Object oriented approach is applied to achieve the main objective it designed. The project is designed to change the existing system in to computerized system and it creates awareness regarding to the agricultural stock market products prices between customer and government. Not only these one but also the system is designed to create stable and balanced agricultural products stock market in the country. The main factors that initiate to develop this system are, the problems with the existing system regarding to product registration, data redundancy, information availability and over all products data handling process. During developing this system we have used different tools for each and every specific parts or components of the system, like XAAP for database designing, HTML & Dream Weaver for webpage designing, Edra Max & Visual Paradigm for user interface designing and Microsoft Windows Operating System for the whole documenting process of the project. So this new system will definitely give overall management solution to these mentioned or expressed issues.
First of all we want to introduce the general idea of the system that we are going to develop. This is a few about the stock market management system for Ethiopian agricultural goods. As technology progress, new applications emerging and replacing the older one. As all other organization, the stock management system has its own standard, mission, statement, vision, power, duties and other kind of views. So that by analyzing and interpreting these entire things, this new system is designed to provide standard and quality services for Ethiopian farmers as well as communities and solve or minimize all the problems with stock market by making it flexible, decreasing the work overload, wastage of time and to be easily accessible for the users. So this system changes the manual marketing system to automated marketing system and well organized in order to solve the problem that faced the present system. 1.2. Background of the Project
Now a days computers are involved in every sector of life, in wide range of application. In this project we will develop stock market management system for optimal sales and stock market management processes. This system will enable us to record and arrange products on the basis of quantity, quality and value. This system will reduce costs for warehousing, transportation, order fulfillment, and product handling while improving customer service. The System will significantly improve stock turns, optimize the flow of products, and shorten routes within a system warehouse or distribution center and it will provide standard and quality services in the market. 1.3. Statement of the Problem
The existing market system is quite tedious, time consuming, not user friendly environment, Difficult to keep old records and less efficient, slow data processing, less accurate in comparison to the computerized system, require much man power and less security control. In the current situation Ethiopia has no computerized agricultural stock market system which can support in overcoming all such problems related with speed, accuracy, security, portability and many more
No 1 2
ID No RET/1199/02 RET/1169/02
E-mail Ameha7@yahoo.com
Analyst y.aster@yahoo.com
3 4
RET/1391/02 RET/1089/2
mihiretadugna@yahoo.com tekeste.ayalew@yahoo.com
Table 1: Team Composition 1.4 Objectives 1.4.1 General Objective The main objective of this system is to develop computerized stock market management system for Ethiopian agricultural products. 1.4.2 Specific Objectives The specific objective of this project is to develop a computerized agricultural stock market management system that will able to:
2
Similarly the specific objective of this project is to provide user efficient working environment. 1.5 Feasibility Study:1.5.1Operational Feasibility:The proposed system is feasible in case that it convert many operation or work done by the worker to computerized work. So it reduces work force. In other case the system may not feasible in case that it cause reduction of some employee from the organization. This may create an environment of joblessness and fear among the employees. So the management must take corrective actions prior in advance in order to start the further proceedings.
1.5.2 Technical Feasibility The proposed system requires trained people to run the system perfectly. And these people include administrator to maintain database and others to handle the system interface. If this condition not satisfied the system is not technically feasible. From the client side, the proposed system require computers with windows operating system and from server side the system require either Linux or window server operating system. 1.5.3 Economic Feasibility With the manual system the operating cost of the system is very high (475,892 birr) when compared to the proposed system (2, 23000, 00birr). This cost may lead the company to be out of the market. But the proposed system requires less cost (2, 23000, 00birr) to cover all employee salary, hardware and software cost which are necessary to perform system operation. Hence the proposed system is economically feasible.
Project Phases
Inception
Project Planning
Transition
Requirement Analysis
Elaboration
System
&
Object Design
Construction
Implementatio n, Testing
Installation
Items
Price
Quantity
Total price
10
80,000,00
Web server
Already exist
Printer
4,000
8,000
Display Monitor
27,000
1,35000,00
Total
17
2,23000,00
The Old manual system cost take 475,892 birr but the new proposed system minimize the cost to 2, 23000, 00birr.
Amount 1 1 4 4
1.6 Scope of the Project The scope of this project is designing a computerized stock market system for Ethiopian agricultural product that will able to record products information, search products either by name or date of registration, update products information, validate products information and generate daily reports regarding to agricultural products selling and buying prices in the market. This project focuses only on Ethiopian agricultural products stock marketing system.
1.10.1 Fact Finding Techniques In order to success this project we will use the various requirements gathering techniques that include the following:
How use it? We use this technique by directly contacting the farmers union officials.
Practical Observation
While using this technique we observe what the situation is look like
Document Analysis
Under this technique we read different statistical records from the farmers union statistical offices
Questionnaires
We apply this method by using telephone and email when we unable to asking the officials directly.
Table 5: Fact finding techniques 1.11 Systems Analysis and Design The system will design using object oriented methodologies. This increases consistency among analyzer, designer implementation and tasting. Reusability of analysis, design and programming
8
1.12 Development Tools To develop the system, we use different system development tools such as: Microsoft Windows XP/7-for the whole document preparation Micro Soft Word 2007/10- to write the document Visual Paradigm and Edraw Max - to design the system user interface HTML & Dream Weaver-to design web page XAAMP- for data base design 1.13 Testing procedures (types of testing used) To test the system we will use the following testing procedures: Unit Testing Integration Testing Performance Testing Security Testing
1.15 Risks and Contingencies The proposed system can be damaged if there is continuous power disconnection from the source station and the data can be lost at that time. To overcome this risk, taking back up by using external storage devices is advisable.
1.16
After finishing this project we assume or expect that it will perform the required functions for what it designed. Proper resources and budget must be set for this project otherwise it may not handle or touch the desired targets and functions. We assume all suppliers have enough stocks, therefore whenever warehouse manager orders items, they can be delivered immediately.
10
Chapter Two Description of Existing System 2.0. Introduction to the Existing System Even though the current system is not computerized, still it provides some services to the societies as well for the country. The current Ethiopian stock market has different activities and applications. The system balances the stock market price, collects and store different products from different suppliers. The problem with the existing system is that it is a manual system which is lead to time wasting and difficult to manage the stock market processing. Such problems are affecting the organizations or countries economical operations. 2.1.Players in the existing system The Players in the existing system has their own responsibility they are listed below with their responsibilities in the system.
Governmentcontrol the stock market activity Farmers/suppliersthe farmers or suppliers prepare and produce different products for the market Distributer the distributors take products either from the farmers or the government and distribute that to the customer or users. Manager-the role of manager in this system is that he/she administrates the database. Store keeper-the role of store keeper is registering the product and keeping the product from damage. Customers the role of customers in the system is that they buy products from the government or the distributor and they are the main source of economy. Employees-the role of employee is handling the system operation.
11
2.3. Registration procedure: Continues registration should be performed by the system manager. The manager must be updating the system and removed products which are not available. The product should be registered in the data base.
2.4. Major functions/activities in the existing system like inputs, processes & outputs Inputs: The store keeper must enter the products information to the database The manager must enter the updated data daily to system database. Process: The system must validate the products full information. The system must display product information. Output:The stock market management system must generate daily reports about the products as well the stock market. The system must enable the society or farmers to get fair services and price respectively.
12
For example report generated in store department is stated below:Storing report from the store department is described below:-
What type of product is stored At which date the product is entered or come to the store At which date the product is sale By how much price the product is sale
2.6. Forms and other documents of the existing systems There are a number of forms and documents that are used in the existing system. In the following Section Sample form are shown remaining is Appended.
Daily stock market report form Finished and unfinished products report
13
14
15
We can describe these problems as follow in terms of their acronym PIECES frame work.
Acronyms and Definitions P I E C E S Performance Information Economical feasibility Control Security Efficiency Service to users
Performance The performance of any system is required to exhibit and meet the needs of users of that system. The current systems performance is weak. This is due to the following reasons: - first the acceptable throughput rate is relatively high; this means the time required from initiation to completion of a particular task is relatively high. This means it may take a week or more days due to its manual operation. Second is the acceptable response time for a particular task is large. So in the existing system a number of performance problems tend to be interconnected rather
16
Takes long time to confirm and sense of balance because of using the manual technique to stock marketing process.
All side view of the stock cant keep or recorded in the proper manner form and then distributed in the manual manner. As consequence such kind of performance of booklet record can cause a problem of ones profile and also redundancy of the record can occur.
Considerable time is wasted to find the stock information: Searching the stock records is gravely time consuming and it is very difficult to find the records of stock in necessary situation.
Input and Output Problems in an Existing System The main input for the current system is stock market record and records of different goods which enable the system to rearrange the marketing process. The system manipulates and manages all of these and other records manually on papers. In the current Ethiopian stock marketing System, the information of a stock is inaccurate, redundant and inflexible, and these in accurate inputs may leads to inaccurate output. Information Problems in an Existing System This slice provides an overall view of telemetric-based public (goods) transport information systems currently in operation or in the process of being implemented. When we compare the existing stock market management System with proposed one; the existing system has many problems relating to information. From those major problems, some of them are listed below:
Security and privacy of stock information is difficult to preserve. Economic Feasibility Problems in an Existing System
Economic feasibility problems in the stock market leads to be unbalanced labor force and debit rather than profit in the organization. This problem can be solved by the proposed system. Generally, the existing system is highly cost. The current agricultural stock market performs all of its tasks manually which requires much of the work to be done by a man power, and a huge amount of papers used for the manual storage of stock data, which lead to spend much money for human resource and for purchasing papers and other materials. Security and Controls problems in the existing system This can be used to protect accessing data and information of stock from unauthorized party when to be shared between the stock market data centers. Controlling and security mechanism of the current system to distribute the product is simply by using different signatures that signed by the authorized person such as the property manager, purchaser manager by checking this, the product will distribute to the users according to their request. This is the security mechanism of the current system. When we come to the controlling mechanism each product is counting daily when drop out from the store. When we see in terms of the existing system, more or less it is affected by this problem.
In accessing ones side view of product, it is not protected. So many products can be un kept properly Accessing and investigation of products information is difficult
18
There is no clear report which stock or product is there or not Service problems in an existing system
The Existing system has gotten a problem in giving service to the users in a way that when scarcity of products are occurred, the system is not as much hurry to supply and knows in such case. The services given to users are not flexible, reliable and expandable. Among the major problems that faced existing manual system are:
Distributing of product at time of need. The users not satisfied by the service on time. Delay of filed record access.
2.8 Practices to Be Preserved The stock market management system that we are going to develop will provide a different service to the farmers or societies. From the existing system the following are practices to be preserved: System procedures
19
2.9 Proposed solution to address or solve problems of the existing system The main purpose of new system that we are going to develop is in order to solve problems that faced the existing system in the functioning of the stock market system, so the system has different alternative options to solve these problems. These are:
Changing the whole manual system in to automated system without affecting the
structure of the organization.
Developing the transaction or well-designed system of the SMMS. Developing customer handling system of the SMMS. Developing easily accessible documents that is clear to employees when accessing data Avoiding wastage of time the manual system during searching products by the
computerized system
The proposed system will be designed to support the following features: The proposed system will include a user friendly Interface for porting of data to The proposed system shall provide the facility to pull the data from the server of the specified The system shall Supply order number and get the respective report.
20
1. Functional requirements These requirements include hardware and soft wares that will used to develop the new system. The proposed system will be designed to perform the following functional requirements:Generate Report-the system shall generate report regarding to the stock market Register New products-the system shall register new products with desired information Search Product-the system shall search and view the product name or information Update Products information-the system shall update products information as the manager order it or input the data. Register Customer-the system shall register number of customers these may use the products Validate User Name and Password to Login-the system check the validity of entered user name and password while the manager or store keeper login. Create Account-the system shall create account for user while ordered. 2. Non-functional requirements This requirement is to checks the systems speed, accuracy, validity and performance. The following are some of non-functional requirements: Performance: - the system shall support Security and access permissions: -The system shall provide security to the database by encrypting user name and passwords. Compatibility:-The system shall run on windows operating system perfectly. Modification-Maintainability:- The system shall easily maintainable
21
22
Sequence Diagram
Class Diagram
The proposed system is to make harmonious and healthy relationship between users and employees. The new system is expected to bring remarkable change in the stock market management system. It documents the products in an organized manner and allow employee to enter data into and query from products record for any of stock market activities.
23
3.1 Use Case of Proposed System Participating actors Manager Store Keeper Customer Employees
Use Cases Register New products Search & view existing Products Generate Report Control Database Operation Use Products Request Products Login Register customer Register Employee Control Stored Products Record finished product
Use Case Diagram the of Proposed System We use this Use Case diagram to show the relationship between actors and use cases of the system.
24
Control Stored Product Generate Report Manage r Register Employee Use Product Employ ee
Search Product
Register Customer
Request Product
Store Keeper
Fig 2: Use Case Diagram Use Case Documentation and Description Participating actors Customer:-Notice to the distributer to take the products that are found in the store room. Store Keeper:-Register, Search products and control the product stored in the stored room.
25
System Use Cases Description Use Case ID: 01 Use Case Name: Register New products Description: This use case describes that the process in which new coming products are Registered. Actor: Store Keeper Pre-Condition: A new products should be provided or available Alternative Condition: Post condition is not succeeding and the system is return back to check the existence of pre-condition.
Flow of Event: 1. 2. 3. 4. 5. 6. 7. 8. 9. The store keeper login in and register the new products to the database. The store keeper enters or type user name and password to login to the system The store presses The Register menu The system displays all Registering under Register menu The stores keeper press The Register Product Menu from The displayed Menu The system displays the Register Product form The stores keeper fill the product information on The Register products form The system validates that all The information are filled The system pop up a data has been saved successfully
26
Flow of Event: Searching the recorded product by name or date that recorded currently Post-condition: Make the product for desired goal and Handle it properly. Alternative Condition: Post condition is not succeeding and then the system will display an error message and return back to check the existence of pre-condition.
Use Case ID: 03 Use Case Name: Control Stored Product Description: This use case is used to distribute the Products for users or government. Actor: Store keeper and Employee Pre-Condition: there should be product available in the storage room. Flow of Event: the store keeper check that whether there is products or not in the storage room and give proper safety to these products. Post Condition: the existence of the product is validated and the product is handled safely.
27
Alternative Condition: Post condition is not succeeding and then the system will display an error message and return back to check the existence of pre-condition. Use Case ID: 0 6 Use Case Name: Register Customer Description: This use case describes that the process in which employee is registering number of users that need the products. Actors: Employee Pre-Condition: There should be Customer those need a product and the product also should be available. Alternative Condition: Post condition is not succeeding and then the system will display an error message and return back to check the existence of pre-condition. Event Flow: The employee take name list of customer from the assigned kebele or wereda. Post Condition: Name list of customer has been saved to the data base successfully. Alternative Condition: Post condition is not succeeding and the system is return back to check the existence of pre-condition. Use Case ID: 07 Use Case Name: Use the Products Description: This use case defines that the process of for whom the product is distributed and who can use it.
29
Pre-Condition: The name list of customer should be registered or known. Event Flow: the customer go to the distributor office or the market and full fill the desired form on the registration form that is prepared by either the distributor or by the government.
Post Condition: The customer gets the products from the distributors or market. Alternative Condition: Post condition is not succeeding and then the system will display an error message and return back to check the existence of pre-condition. Use Case ID: 08 Use Case Name: Request Products Description: This use case describes the process what type of products the customer need and what pre-Condition should be fulfilled before they take the product. Actor: Customer Pre-Condition: There should a form and the customer must get and fill that form with required information. Flow of Events: The customer writing the product name in the form and ensure that he/she want that product. Post Condition: The form is completed or filled with required information. Alternative Condition: Post condition is not succeeding and then the system will display an error message and return back to check the existence of pre-condition.
30
Use Case ID: 09 Use Case Name: Record finished Products Description: This use case describes the process in which finished products are available for market or for users. Actors: Store Keeper Pre-Condition: There should be list of finished products Event Flow: the store keeper get name of products and record it to the database and send it to the manager. Post Condition: list of finished products saved to the database successfully. Alternative Condition: Post condition is not succeeding and then the system will display an error message and return back to check the existence of pre-condition. Use Case ID: 10 Use Case Name: Login Description: This use case is used to allow the stores keeper and manager to enter to a system Actor: Store keeper and Manager Pre-Condition: authenticated or authorized User Name and password in the account for store keeper and Manager.
31
3.2 Sequence Diagram We used sequence diagram to describe the interaction between actors and objects of the system.
1. Manager login 2. Store keeper Login 3. 4. 5. 6. Register New products Search & view existing Products Generate Report Register Customer
32
Security login
System Database
Main page
Manager Open page Enter u.n& Psswrd Check u.n& Pswrd Login success Open page Enter wrong u.n &pswrd Verify u.n& Pswrd
The above sequence Diagram expressed as follow:1. The Manager open home page and click on login 2. The Manager enter user name and password
33
Security login
System Database
Main page
Store Keeper Open page Enter u.n& Pswrd Check u.n& Pswrd Login success Open page Enter wrong u.n &pswrd Verify u.n& Pswrd
34
Store keeper
Registration Form
Registration Controller
System Database
Save Ok
C ck Product he N e am
35
The above sequence Diagram expressed as follow: 1. 2. 3. 4. The store keeper identify information about the new product The store keeper register that product with proper name The system verify or check the product name If the name of new product is not registered before a time the system will save it in the data base. 5. If the name of the product is duplicated or already exists then, the system will displays this product name is already exist. 4. Product Request Sequence Diagram
36
Request Form
Request Controller
System Database
The above sequence Diagram expressed as follow:1. 2. 3. 4. The user enters or fills the name of product he/she wants in to the request form. The system check or verify the existence of that product in the database If the product exists then, the system will display this product is available message. If the product not exists then, the system will displays this product is not available.
37
Store keeper
Searching Form
Searching Controller
System Database
1. The store keeper enters the name product he/she want to search. 2. The system verify name of the product and start searching. 3. If the store keeper enters correct product name then, the system will display that product name. 4. If the store keeper enters wrong product name then, the system will displays products name is not exist message.
38
Daily Report
Report Form
System Database
Main Page
Display Report
The above sequence Diagram expressed as follow:1 2 3 The Manager open home page and click on login The Manager add the reports to the database system The system verify the reports and display the daily report form
39
SMMS Apploication
Update() Delete()
Logout
40
41
Customer
Cust_Name: String Cust_ ID: String Cust_Address: String Request Product () Use Product ()
Manager
Store Keeper
inherit Manager Name: string Manager ID: string Manager PhoN: int
Store Kpr Namee: String Store Kpr ID: String Store Kpr PhoN:int Login () Register Nw Prdct () Register Fnshd Prdct () Generate Report () Search Product ()
Login () Generate Report() Control Database Operation () Employee 1 * Employee Name: String Employee ID: String Employee PhoN: String Register Customer () Control Stored Product ()
3.5 User Interface Prototyping This section illustrates some of the user interfaces that are included in the proposed system.
Desk Top
Login
Manager
Store Keeper
File
Create account
View
Open
Search
Exit
Report form
Registration Form
Distribution Form
43
4.0 Class Type Architecture We design the proposed system based on the information established in the requirement document. The architectural strategy that we follow to develop this system is used us to layer the architecture of a system into several layers. The following figure presents a high-level layering strategy for a software application. The various layers are represented by the rectangles and collaboration between layers by the arrows. The primary name of a layer is indicated first, and other common names in parenthesis. Those Architecture layer are listed below and they will be discussed in the below table one by one: User interface Layer Controller/Process Layer Business /Domain Layer
44
System System
Layer Layer
Domain/Business Lyr.
Employee Finished Product User Request Product Farmer Store Keeper Register Product
S Y S T E M C L A S S
SMMS DB
45
Description of each class Type Architecture Layer Interface Layer Description This layer wraps access to the logic of the system. This layer provides access to user of system and external access to system. Skill set For user interfaces:
User interface design skills Usability skills Ability to work closely with stakeholders
Domain Layer
This layer implements the concepts relevant to business domain such as material, focusing on the data aspects of the distribution objects, plus handling the material.
Analysis skills to identify domain classes Design skills to determine how to implement the domain classes Domain modeling skills, in particular UML class modeling Analysis skills to identify process classes and process logic Design skills to determine how to implement the process classes Modeling skills, in particular modeling, flow, and sequence diagramming
Process Layer
The process layer implements business logic that involves collaborating with several domain classes or even other process classes in the system.
46
Object/relational(O/R) mapping Architectural skills so we can choose the right database encapsulation strategy Modeling skills, in particular class modeling and physical data modeling Analysis skills to identify what needs to be built Architectural and design skills to determine how to implement the classes Modeling skills, in particular class modeling, sequence diagramming, and state modeling
System Layer
System classes provide operating-systemspecific functionality for the applications, isolating the software from the operating system (OS) by wrapping OS-specific features, increasing the portability of our application.
In this model we illustrate the software components that used to build the proposed system. We build it up from the class model and written from scratch for the new system. These Components are high level aggregations of similar software pieces, and used to provide building block approach to software construction.
47
y cr en t ion p
da ac ta ce s s
da ac t a ce s s
We use this diagram to show the physical view of the proposed system, bringing the system into the real world by showing how software assigned to hardware and how the pieces communicate. It is also used to show a collection of nodes and also dependencies of associations among them. The associations between nodes Represents a physical connection. The deployment diagrams we used show that the hardware for the proposed system and the software that is installed on that hardware and the middleware used to connect the disparate machines to one another.
48
acc e c on s s trol
4.3 Persistence Models We design Persistence models for the proposed systems are used to communicate the design of database, usually relational database, with the user and actors. This is basically the entity relation in database application. The system that we design overall persistent modeling is described as class modeling part it described as follow:
49
* 1
50
User interface design shows the interfaces of our system how it interacts to its users. In the following section we are going to show the UI design and we are going to use to our window application system. Login Screen 1. 2. 3. 4. This screen requires keyboard input. Users will see two boxes for entry of user name and password. The purpose of this screen is to identify a user of the Stock market management System. Upon entering a valid user name, the system continues on by requiring a password for entry into the system. 5. If the user name entered is that of an administrative user, the system will display the administrative main menu.
51
Stock Market Management System Main Menu Page The main screen is displayed when the terminal is started and is returned to whenever a user finishes a session. Its purpose is to display welcome message to the user and enable the manager to Customize the page by placing different documents and files related to the stock market. It is an interface that allows a user quick and easy access to specific sections of the stock market management System. After login the user can view document or file and also can ask help from the system.
52
Account Creating Page The account creation page is used to create authorized user account. Under this page only two users can create the account. This means that the only the manager and the store keeper. It is also possible to list down type of account created in the system database
53
This page is used to view or display the daily report of the stock market, the stored products and also added products.
New Product Registering Page The main function done under this page is that registering the new products to the database. This page is mainly accessed by the store keeper. Because registering the new products is the main function of the store keeper. It is also possible for the user to update and delete the products information.
54
Fig 11.4: New Product Registering Page . Product Requesting Page The product requesting page is used to identify that what type of products and how much quantity is required by the user. Under this page it is also possible to check that amount product is available. This help to compare number of user asking the products and amount of product available.
55
Product Distributing Page The main application or access takes place under this page is to identify that what type of products are distributed, amount of product distributed, remaining, amount of product receipted, by how much value or price the product distributed. For distribution purpose the products information can be added or updated under this page.
56
Product Searching Page This screen enables the user to search information about the products these has been registered in to the system database. The user can search the products specifically either by products name or date at which the product is registered.
57
58
The purpose of this chapter is to provide some basic highlight of the issue dealt with the implementation phase. During implementation the physical operation specification is turned into working computer code. Then the code is tested until most of the errors have been detected and corrected. The goal of implementation is to check that whether or not the proposed system is work correctly or to check that is that it gives the required output.
Overall design of the system algorithm is based on its class diagram or persistence diagram relationship. This mean each form created for the new proposed system is based on corresponding representation in the database table. We started the system coding during the beginning of design. That is, there is coding during user interface implementation, database implementation, and logical implementation. Our system has too this described code to be appeared them as sample code at the end of this chapter.
Testing evaluates a software product to ensure that it satisfies its planned purpose. A test that is modified to and consistent with development methodologies provides an observable and structured approach to verifying requirements and quantifiable performance. To test the system we use the following testing mechanisms:
Unit Testing: - we test individual program module or component; they test it to ensure that it works according to specification, operates within acceptable parameters, and meets the appropriate standards.
59
Security Testing:-Security testing was done by trying to access the system that is not authorized. This means without the valid user name and password we try to access the system. Performance Testing:-Determines how the system performs on the range of possible environments in which it may be used. This test is done by configuring the system in different environments like different operating systems, different networks and different hardware configurations. 5.4 User Manual Preparation
License Agreement: - The following is user's license agreement for stock market management system. This User License Agreement is a legal agreement between you and the software maker. By installing, copying, or otherwise using the software product, you agree to be bound by the terms of this agreement. If you do not agree to the terms of this agreement, do not install or use the software product. Copyright:-The software product is going to be protected by copyright laws and international copyright agreement, as well as other intellectual property laws and treaties. Compatibility:-The software is compatible with Office 2003-10 and Windows XP or Windows 7 operating System.
5.5 Training The overall system is although taking consideration of user-friendly style. Therefore during system deployment it needs giving simple highlight about system. This training consists of two
60
User can simply start the page through using the desktop short cut or by entering to all program files.
1.
Test Cases Test Case 1 Customer Registration Test Case ID =SMMS-TestCase01 Unit to Test = Registration of Customer Assumptions = Congratulations! Test Data = FirstName (invalid FirstName, Valid FirstName, empty) UserID (occupied username, valid username, empty) Password (invalid password, valid password, empty) ConfirmPassword (didnt match with password, valid, empty) Email (invalid Email, valid Email, empty) Steps to be Executed Data Empty FirstName and all others filled and Click register button Invalid FirstName and Click register button Enter valid First Name, empty UserID and Click register button Any valid data for the other fields FirstName=@ameha FirstName= Ameha Any valid data for the other fields
Expected Results
Error: First Name cant be blank Error: First Name must contain only letters, numbers and underscores! Error: UserID cant be blank
61
62
Sample Code
<HTML> <HEAD> <TITLE>Home stock</TITLE> <script>window.start_time = new Date ().getTime ();</script> <SCRIPT type="text/javascript" src="stock styl js/textscroller.js"></SCRIPT> <script type="text/javascript" src="stock styl js/script(1).js" charset="utf8"></script> <link rel="stylesheet" href="stock styl js/style.css" rel="stylesheet" type="text/css" /> <link rel="stylesheet" href="stock styl js/style2album.css" rel="stylesheet" type="text/css" /> <link rel="stylesheet" href="stock styl js/style(6).css" type="text/css"> <script>window.Bootloader && Bootloader.done(["pJWab"]);</script> <script src="styl js/jquery.js" type="text/javascript"></script> <script type = "text/javascript"> var count = 3; function validate() {
63
64
65
<td width="115"> <nav id="main_menu" class="clearfix" role="navigation"> <ul class="dropdown sf-menu nav"> <li> <a href="stock market home.html" title="Home" target="blank">Home</a> <td width="150"> <nav id="main_menu" class="clearfix" role="navigation"> <ul class="dropdown sf-menu nav"> <li> <a href="stock market price.html" title="Tody's Price" target="blank"><span>Tody's Price</span></a> <td width="110"> <nav id="main_menu" > <ul class="dropdown sf-menu nav"> <li class="dropdown" id="profile_dropdown"> <a href="stock market commodity.html" title="Commodity" target="blank"><span>Commodity</span></a> <td width="144"> <nav id="main_menu" > <ul class="dropdown sf-menu nav"> <li class=" archivio_ethiopia"> <a href="stock market about us.html" title="About Us" target="blank">About Us</a> </li> <td width="145"> <nav id="main_menu" class="clearfix" role="navigation"> <ul class="dropdown sf-menu nav"> <li> <a href="stock market contact us.html"title="contact Us" blank" target="blank">Contact Us </a> </li> <td width="11"> <nav id="main_menu" > <ul class="dropdown sf-menu nav"> <li class="dropdown" id="profile_dropdown"> <a href="stock market help.html" title="Help" target="blank"><span>Help</span></a> </li> <td><form method="get" id="search" action="http://www.google.com/custom" target="_top">
66
67
68
</div> </div>
</div> <TD bgColor="#222" width="57%" height="701"border="3" > <div style="background:#1E4D2B; padding: 15px; margin-left: -9px; marginright: -9px; -moz-border-radius: 25px 25px 25px 25px; border-radius: 5px 5px 35px 35px;"> <h2 align="center"> stock market</h2> </div> <br><br>
<embed src="image.swf" width="45%" height="30%"> <p>The Ethiopian Commodity Exchange (ECX) announced it will further strengthen the warehouse receipt financing scheme during the opening of the Warehouse Receipt System for Inclusive Agricultural Finance Symposium.<img src="Latest%20Business%20Alerts%20_%202merkato.com_files/ecx.jpg" align="right" border="0">
69
<TD bgColor="#222" width="100%"> <div class="divider"></div> <embed src="image/clock-calendar-002.swf" width="100%" height="30%"> <div class="divider"></div> <br><br><br><br>
<form name = "myForm" action="demo_form.asp" onsubmit="return validateForm();" method="post"> <p>Enter Email<input type="text" name="username"><br><br> <input type="button" value="Subscrib" name="Submit" onclick= "validate()"> </p> </form> <br><br><br><br> <a href="stock market coment.html" title="hotmail" target="blank">Comment</a> <div class="divider"></div> </TABLE><br><br> <TABLE align="center" width="100%" height="22%" bgColor="#1E4D2B" border="0" cellSpacing="8" cellPadding="0" >
Chapter Six
70
6.2 Recommendations We would like to recommend that anyone has not right to add functionalities; customize the system as needed to improve the overall functionality of the system. Because we will continue for the next year final year project. We would like to recommend the government, to use the better way of managing the stock market system, because the current system has some drawbacks and is manual. As a result we are proposing a new mechanism system to the stock market system.
71
References
1. Books
Software Engineering (2011) 9th edition By Lan Sommer Ville System Analysis and Designing EIGHTHEDITION By KENNETH E. KENDALL Rutgers University School of BusinessCamden Camden, New Jersey JULIE E. KENDALL Rutgers University School of BusinessCamden Camden, New Jersey The Unified Modeling Language Second edition By James Rambough, Ivar Jacobson and Grady Booch. The Elements of UMLTM2.0 Style Scott W. Ambler Object oriented system analysis and design By Simon Bennet, Steve McRobb and Ray Farmer
2. Internet Sites
www.weekipidia.com www.codeproject.com
72