The London Visual Arts Exhibition System - Case Study Example

System Requirements Specification Table of Contents Introduction 3 Plain and s of Business Events 4 Table of Events 5 Schedule (Gantt chart) 6 Phases of the Development Plan 6 Requirements identification and analysis 6 System Design 7 System testing 7 System implementation 8 System maintenance 8 Context Diagram and Level0 data flow diagram 9 Context Diagram 9 Level0 data flow diagram 10 Entity Relation diagrams 11 References 13 Introduction The London Visual Arts (LVA) exhibition system is an online management portal that delivers support to both the artists and its management staff at the LVA Gallery via the computerized system. The LVA Gallery system includes features that will enables the LVA managing director of deal with exhibition events and plan on each event accordingly. The clients in this particular case will be the artists who are interested in getting their painting exhibited in the Museum/Gallery. This writings in this document highlight the data flow diagrams that showcase the flow and movement of information within the system. The major entities involved in the operations of this system involve the museum management staff, the curator, the artist, the promotional artist, the transportation agency and the advertising agency. The reservation requirements would include date, time and duration of stay, and each customer or artist will be required to register on the website when providing painting information. Plain and Abstract Descriptions of Business Events The business events entailed in this system mainly focus on the marketing of exceptional paintings via the London Visual Arts (LVA) Museum/Gallery. Artists will have to contact the London Visual Arts (LVA) Museum/Gallery curators and upload snapshots of the paintings they are interest in displaying at the exhibition. In turn the London Visual Arts (LVA) curators examine and select paintings that would make a good exhibition. Curators also contact other galleries or museums to find out about paintings held elsewhere viable for exhibition. Paintings collected and scheduled for exhibition are transported to the London Visual Arts (LVA) via a transportations agency. Next, the curators create a detail file for each and every painting to be put up for exhibition together with all the artist information affiliated to the respective painting. The business events meant for this system revolve around the operations manager, that is, the curators at the art gallery who are responsible for managing the major operations of the proposed system, a term referred to as a system administrator (BURAGGA & ZAMAN 2013). Table of Events Event Trigger Source Activity Response Destination Artist wants contact curator Contact Curator to inquire for exhibition Artist upload painting snapshots/details painting details delivered Curator Museum/gallery wants contact curator Contact Curator to inquire for exhibition Museum/other Gallery upload painting snapshots/details painting details delivered Curator Curator wants to contact artist contact artist Curator email artist with acceptance/rejection details accept/reject email details Artist Curator wants to contact other museum/gallery contact other museum or gallery Curator email other museum/gallery with painting acceptance/rejection details accept/reject email details Museum & other Galleries Curator wants to check room availability exhibition room inquiry Curator check room availability room availability details Curator Curator wants to send exhibition details update artist or museum Curator submit exhibition information exhibition details Artist, Museum & other Galleries Curator wants to contact promotional artist inquiry for advertisement Curator submit exhibition dates information promotion date details Advertising agency Curator wants to contact transport agency inquiry for transport Curator submit artist or other gallery contacts artist or museum and other gallery contacts details Transport Agency Schedule (Gantt chart) ACTIVITY WEEK 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 Project description Project proposal Literature review Project plan Functional specification Software design Coding Software testing Implementation Documentation Phases of the Development Plan Requirements identification and analysis This phase of the development cycle is tasked with preliminary investigation of the end user needs. The end users of the system in this case scenario will be patients, doctors and physicians who will interact with the end system after its development. This stage of the software creation promotes project planning and he feasibility study to be carried out. This aids in establishing a high level view or display of the intended project and determines the objectives set for the organization. This stage entails data collection of facts and figures and other data variants which involves a feasibility study which is purposed to aid in the carrying out of an economic study of the organizations background (SEFFAH, GULLIKSEN & DESMARAIS 2005). Subsequently, an analysis of collected data should be carried out to identify and define the requirements for the user and proposed system via refining the project objectives into definite operation and functions of the envisioned application. This study requires the use of tools that examine the system process and facilitate better analysis. Examples of tools are the use of DFD and ERD diagrams for entity relational and representational activities in the analysis of end user information needs. System Design This stage of the software system development cycle involves the actual creation of the system via the use of design tools, for instant the various programming platforms used for development of software that run on numerous end user operating system. Here, the features and the operational specifications of the desired system are planned and described in detail. The interfaces and layout of the proposed system are noted down in this stage. Graphical user interfaces and human computer interaction devices and instances are implemented in this stage for the intended system. This gives the designers to practice and impart their skills, technical knowhow and innovative approaches in developing attractive and easy to use end user interfaces for their customers (SCHWALBE 2010). This is done in consultation with the clienteles of the end proposed system while keeping in mind the design of the system from their approach as well. In this case the user interfaces of the different end users like the doctors, patients and the physician portals for login and the creation of the various databases to represent and aid in data storage of end user details. System testing This is a segment of the development progression that brings all the modules of the system together for use in an exceptional test environment with the aim of identifying the compatibility of the system with the intended environment it will be operating on. Its reliability, interoperability and flexibility are noted at this stage. The end user memorability and technical knowledge to interact with the system are identified at this stage and feedback collected to find out if the customers are content with system operations and executions. In the case of any need for any rectifications is done at this stage via the identification of errors and bugs in the integrated system environment. If the organization is content with the system then the implementation is carried out. System implementation This is the actual installation of the system and acceptance of the system in the intended environment. Initially software systems are developed to ease and simplify daily work operations via fast execution and processing. The implementation of the proposed system comprises and organization shifting from there old system to the novel one. The successful installation of the system involves training of personnel on how to use the system and adapt to the newly employed system (LANGER 2012). System maintenance The maintenance of a system is the subsequent activities carried out on the system to ensure its constant operability and consistency in execution and processing of the info that the software platform utilizes. System maintenance entails the rectification of errors and the removing of bugs (debugging) the overall software code. Other activities include the upgrading of the software frameworks to higher introduced and developed versions. This is usually a long term period of the project where there is always need for correction, addition, change of the modularity, simplifying any complexities and changing the technological operating systems to adapt to new and enhanced software metrics. Context Diagram and Level0 data flow diagram A context diagram represents a data flow diagram which showcases the generalized function of each entity in relation to the proposed technological system. The graphical visualization is shown below exhibiting the processes between the different entities and the LVA system components. Context Diagram Level0 data flow diagram Entity Relation diagrams The ERD represent the relationship between the different entities of objects or concepts within the proposed information system. The content in boxes represents entities; while the diamond shaped drawing represent the actions taken by the respective entities. The content in circles of the ERD characterizes the attributes of each and every entity. References BURAGGA, K. A., & ZAMAN, N. (2013). Software development techniques for constructive information systems design. Hershey, PA, Information Science Reference. http://site.ebrary.com/id/10679155. LANGER, A. M. (2012). Guide to software development designing and managing the life cycle. London, Springer. http://site.ebrary.com/id/10523860. LANGER, A. M. (2008). Analysis and design of information systems. London, Springer. SCHWALBE, K. (2010). Information technology Project Management. Boston, MA, Course Technology/Cengage Learning. SEFFAH, A., GULLIKSEN, J., & DESMARAIS, M. C. (2005). Human-centered software engineering integrating usability in the software development lifecycle. Dordrecht, Springer. http://site.ebrary.com/id/10134045. Read More