Download System Analysis(Art Gallery) and more Lab Reports Software Project Management in PDF only on Docsity!
3.1 System Design
Systems design is the process of defining elements of a system like modules, architecture, components and their interfaces and data for a system based on the specified requirements. It is the process of defining, developing and designing systems which satisfies the specific needs and requirements of a business or organization. A systemic approach is required for a coherent and well-running system. Bottom-Up or Top-Down approach is required to take into account all related variables of the system. A designer uses the modelling languages to express the information and knowledge in a structure of system that is defined by a consistent set of rules and definitions. The designs can be defined in graphical or textual modelling languages. Some of the examples of graphical modelling languages are Unified Modelling Language (UML): To describe software both structurally and behaviorally with graphical notation. Flowchart: A schematic or stepwise representation of an algorithm. Business Process Modelling Notation (BPMN): Used for Process Modelling language. Systems Modelling Language (SysML): Used for systems engineering.
3.1.1 System Design Methods
a) Architectural design: - The architectural design of a system emphasizes the design of the system architecture that describes the structure, behavior and more views of that system and analysis. b) Logical design: - The logical design of a system pertains to an abstract representation of the data flows, inputs and outputs of the system. This is often conducted via modelling, using an over-abstract (and sometimes graphical) model of the actual system. In the context of systems, designs are included. Logical design includes entity-relationship diagrams (ER diagrams). c) Physical design: - The physical design relates to the actual input and output processes of the system. This is explained in terms of how data is input into a system, how it is
verified/authenticated, how it is processed, and how it is displayed. The physical portion of system design can generally be broken down into three sub-tasks: User Interface Design Data Design Process Design User Interface Design is concerned with how users add information to the system and with how the system presents information back to them. Data Design is concerned with how the data is represented and stored within the system. Finally, Process Design is concerned with how data moves through the system, and with how and where it is validated, secured and/or transformed as it flows into, through and out of the system. At the end of the system design phase, documentation describing the three sub-tasks is produced and made available for use in the next phase.
3.2 Design strategy and Module
Design strategy: - A strategy or approach to project design management explains how to perform stated goals with available resources. Such a strategy will be the basis for developing project activities and tasks. In my project, I considered my past experience from an existing project. I learned some important lesson from those project. In which kinds of modifications and additional features for design is required. Firstly, I set a primary goal of future design strategy and build my strategy incrementally to establish a clear path for achieving the goal. My work design is decomposed in activities, project phases and steps as a task of my design strategy. Module: - A module in project is a high-level description of a functional area, consisting of a group of processes describing the functionality of the module and a group of packages implementing the functionality. In this section, I have explained all the modules of my project. Modules are the very first part to be discussed during the development the project. The project is divided into different modules. Some of them is dependent and some are independent. All these modules are managed by PMM (Project Module Management). This project is divided into partially dependent and independent modules as:
Some modules are from administrator side: -
3.2.8 Administrator Page: - From the login page, providing his/her
administrator ID and password, he/she can access the administrator page, that shows the administrator menu to access all the administration activities (manage items, manage users, manage categories).
3.2.9 Manage Categories: The administrator can access and modify all data
about categories stored in the database, add a new category and also delete them. The administrator can delete a category if and only if no items are associated to that category; otherwise an error message is raised.
3.2.10 Manage Items: - The administrator can access all data about items stored
in the database and also delete them, but not modify the characteristics of the items (initial price, description etc.).
3 .2.11 Manage Users: - The administrator can access and modify all data about
users stored in the database and also delete them.
3.2.12 Accept / refuse auction: - The administrator can control the new
auctions posted by the user and decide whether to accept or to refuse them.
3.3 Data Flow Diagrams
Data flow diagram is used to decrease analysis the movement of data through a system store of data in the system. Data flow diagrams are the central tool basing on which components are developed. The transformation of data from input to output, through process may be describe logically and independently of physically components associated with the system. They are called logical data flow diagrams. In contrast physical data flow diagrams show the actual implementation and movement of data between people, Department, and work station. A DFD shows the flow of data through a system with all its processing entities. It views the system as a function that transforms the inputs into desired outputs. A data will typically undergo a series of transformations before it becomes the output. The DFD aims to capture the transformations that take place within a system to the input data so that eventually the output data is produced.
Symbols used in DFD Source or Sink; Source: is where the data originates Sink: is where the data terminates Data Flow Bubble: is process or procedure agent Temporary Storage or External File Rules for DFD Each process should have at least one input and an output. Each data store should have at least one data flow in and one data flow out. Data stored in a system must go through a process. All processes in a DFD go to another process or a data store. Label data flow on each arrow. Use details flow on each arrow. Use the details flow arrow to indicate data movements.
3.3.1 DFD levels and layers
A data flow diagram can dive into progressively more detail by using levels and layers, zeroing in on a particular piece. DFD levels are numbered 0, 1 or 2, and occasionally go to even Level 3 or beyond. The necessary level of detail depends on the scope of what you are trying to accomplish. The data flow diagram show functional composition of the system. The first level of conceptual level in context diagram is flowed by the description of input and output for each of entities the next level of DFD is level 0, which shows the main
In Art Gallery system there is a module called administrator. First of all admin of the system has to login using their admin account. After login administrator have some facilities. Admin can view all the items. Admin can add new category for the other modules. As art gallery supports auction system all the bids placed on the product admin can view all of them.
Second module in Art Gallery is Artist. Here artist can sell their art after successfully login. If Artist does not have account he/she can easily register. An artist can view his products, can choose categories, view bidding info and sale at higher bid on the product.
After that user can logout their account. But members and Artist can see all the products available in art gallery. After logout member can’t place a bid on products. Artist also can’t post an auction for bidding.
Fig. 3.4.1 Flowchart of Online Art Gallery
3.5 Database Design
3.5.1.3 contact_form table This table contain the info about the person who contacted us via art gallery contact us module. 3.5.1.4 admin_login This table contain the login info about the administrator. Online art gallery system can have multiple admins.
3.5.1.5 add_painting Through this table artist can add new painting to Online Art Gallery System. This table contain information about artist name, painting title, price, image etc. 3.5.1.6 bidreport table This table contain all the info about paintings bids. Who is the highest bidder of the paintings? It also have foreign key that connect with customer info. This table tracks all the bidding logs. 3.5.1.7 artofmonth table Online Art Gallery system have a table which tells the best art of the month. This depends upon which painting timestamp is more updated.
Fig. 3.5.2.1 ER Diagram of Online Art Gallery The ER Diagram of the project Online Art gallery described us username and password have Entire access to the system. All of them needs username and password to use art gallery system. Member can bid on product after successfully login. He can see the product name, description, image etc. Artist can upload new auction to system according to given categories. At last admin have some different responsibilities manage members and artist, categories, products, biddings etc.
