System Analysis and Design for Ticket Sales System

Analsysis of the task fr the purpose of assignmning responsibility for the system compnents.

System analysis and planning:

The first process taken is the system analysis and planning.  This is a process that involves identifying of the system objectives, the key functionalities and the system specific objectives. One of the key specific objectives that the team come you with according to the case study is to make a website that will help in displaying of digital product.

The system must have a customer section which enable the users to reach the customers who would wish to register and to book tickets.  From the layout, there should be a dynamic sections in this the customers can interact with the customer care screw as well as the system admin. Dynamic section that is to be included includes login, the sign in, and the questions. Before any customers login, the customers must register and their information stored in the database. The login and the signup functionality allow the admins to monitor the needs of the customers without any challenge.

The designed such that the customers are also able to make their choice of the seats they would wish to use while travelling. This means that customers will have to pay their transport before them logout of the system simply because they make the have to retain their booked seats.

System design process.

From the case study, it is clear that the system design process covers the hardware, the software and the human platforms. The team has to meet and decide the type of the hardware requirements, the software requirement and type of professionals needed to achieve this tasks. The system also describes the detailed system components and how this component relates to each other. System design can be Brocken down into several parts or component. The component includes: logical design and physical design.

Logical design: this is a process that involves deign of a logical data flow diagrams. As the team draw this diagrams, they also define and explain data that this diagrams contain. In addition to the diagram, the type of database the system will use is also described (Light, 2009). After the presentation of the three components the system security is well-presented as well as the backup procedure that the system will constitute.

Physical design:

The case study presents a physical design of the system. This design translates the logical design into physical component. In the ticketing system, physical design states the servers that the

 Medallion theatre will use, system security and the web database to be implemented.  Fr the web servers, the company needs a serious web server component with very fast computers with stable capabilities.  The company also needs a web server software component and the best operating system.

Building the system:

This process requires the group to follow the clear logical and physical design procedures. It actually involve having a complete understanding of how a system is built. In the group there are programmers who will ensure that the system layout is well presented and all the data diagrams are coded. Apart from the system programmers, there are also database management personnel who will be responsible for developing databases. This is because the ticketing system has several databases. The first database is the registration database, the second database is the selection database. This database according to the case study must be integrated with the system.  After coming up with the system shell and working database, the team will come up with the specific components which will be useful for the system.

The case study puts more emphasis on the user interface. According to Dr. Thomas, User interface is an area where the customers get to have a close interaction with the entire organization. The team then resolved to keep the section very simple and easy to navigate. The user interface for this system in this case includes the login form, the menu bars and the picture.

Apart from the above mentioned areas, the user interface also include the admin areas. This an area that I not always visible to the normal users but only the people who have certain advanced privilege on the system.

System testing:

After the ticketing system is done, the case study by Dr. Thomas Demonstrates that it is necessary to test if the system does what its intended purpose was. From the diagrams in the case study, it is noted that this stage is important because provides a solid confirmation that the system will meet its objective and will conform to its specification. To ascertain the system suitability, the system analysis and design process requirement state that it should be taken through different stages.  The first stage is to test individual components. This makes sure that all the component are functional. After the individual testing, the entire system will be put into test. When the entire system is tested, the type of test is known as the unit testing. 

It is important to mention that when fault I found in the system during testing, the module is then taken back to the project team. The project team will be responsible of what could be the challenge of the module and as result correct the problem. Another serious testing is the functional testing. His involves the use of simulation to test the system scenario. Finally the feature test will crown the entire testing process.

Implementation and maintenance:

Implementation and maintenance is the final step in the system analysis case study. In normal cases, the step involves putting the system into its proper use. The professionals who developed the system are offer support to the system as well as showing the users how the system work and functions. This means that nothing is expected to go wrong in the implementation stage. The case study provides a suggestion that the MEDALLION THEATRE should put implementation schedule in place to enable it have a smooth transition of system. This schedule will be follows by the users and the administrators of the system.

Together with the system implementation is system maintenance. This is a process that involves code debugging in attempt to remove the errors that may involve in the coding. The support team must be always on standby to update the status of the seats and the movie titles.

Finally, it is important to note that the success of this system entirely depends on the support dedication. Base on this fact, all the employee are encouraged to offer support to customers whenever they are in a position to do so.  The case study provides a suggestion that the team that should be set aide to perform maintained duties includes the programmers, the designers, database administrators and the managers. This will ensure that the system works smoothly without any problem.

Collaboration and cooperation.

Based on the above discussed task that the system had to go through, the case study seeks to involve student in the design of the system. In doing so, each and every student will be given a task to accomplish. This tasks will be given based on the specialization and the strengths of an individual. This means that a members of the group cannot be given a task that they are not able to handle. Secondly, the task and duties given to each member will be reported on a weekly bases by the project manager who is also a member of the group. The supervision is to ensure that the members are still going as per requirements. 

Information system project management and proect techniques.

It is important to note that ticketing system can be a desktop or even online. Due to this, the team tasked with coming up with this system must work extra hard to ensure the outside world get to use the system without any problem. Due to this fact, the system must be integrated with other online system or must be hosted online to enable user’s access it whenever they are.

Teamwork Nad Leadership

From the case study, the system receives a good and positive participating from the team. At the beginning every project member were encouraged by DR. Thomas states developing the system was very possible. He did this by giving orientation to each and every member of the group.  He also found out how MEDALLION THEATRE operates.  I proposed to the team members that getting more clarification would be a noble step towards the success especially in ensuring that we meet the goals and objectives of the ticketing firm.

Collective decision making:

From the case study, it is evident that all the member made a collective decision based and the influence of Dr. Thomas. The contribution of any member was considered without any biasness. After the opinion of the members were recorded, Dr. Thomas used this to allow the student arrive to their verdict. This means that no verdict went contradictive to the expectation of any student.

Team member support:

For this project support is a key important factor especially from the team member who are entrusted with executing the project.

GROUP REPORT BASED ON THE ANALYSIS OF THE SELECTED CASE STUDY REQUIRING A SYSTEM ANALYSIS AND DESIGN.

According to the case study, there were several process that the system team had to understanding. The key process includes, the design process, the development process and the lounge process. To ensure that all this process become successful, all the group members were allocated a role. This role involves conducting and presenting a good structural research. The process become more successful due to strategic approach the team members gave to the project.

The planning process actually started when the team members called and arranged for the meeting and actually Dr. Thomas stated the expectation of the project.

Leadership

Again as stated before, the planning stage began when the member were called and the purpose of the project stated. This process was initiated by the project team leader who was responsible for making sure that the students understood the purpose of this project. The system meetings were made less formal simply because most of the team leaders had already briefed that project team on his expectation and this made it very easy for the students to do what they were expected to do (Phillip & Nagle,2007). This also means that there was no time wasted in the discussion but went straight to the point concerning the   project.

Communication Style.

All the members were given responsibility of developing an effective communication strategy. To be more effective one major communication style that proof perfect was physical meetings. The leadership of the group convened several meetings that were meant to discuss the challenges and the project progress.  Apart from the physical meetings, the teams also used email to communication important information to the group.

Milestones.

The team members were supposed to record the project milestone at every level without fail. According to the plan, some milestones were to be achieved after a certain period of time. This is because to milestone was meant to be subjected to scrutiny to make sure that objectives were achieved. The team members

Challenges Arising In Collaborative Work

Meeting the objectives of the project.

One key challenge that the project team faced was meeting the objectives of the project. Since the project was a huge project and the student did not have experience with such project, it is expected have a challenge on meeting the project objectives (Nooteboom, 2008). This means that the team has to work extra hard to ensure that they meet the project objective. In addition, the team also has to ensure that they work hand in hand with the project initiators form proper guidance on what is expected in the project.

Time management.

Since the project involves team work and tam understanding, the project timeline was very limited. Acceding to the case study, Dr. Thomas stated that the theater needed the ticketing software as soon as possible and this means that the team had to work with limited time. This becomes a challenges since not every project team member is a good time manager and if not pushed the project could have delayed.

Lack of proper resources.

Since the theater did not understand what the project team member were to do, the team members did it a little bit hard to get all the required resources and this means that their work was not easily executed.  

References

Phillips, C. L., & Nagle, H. T. (2007). Digital control system analysis and design. Prentice Hall Press.

Hoffer, J. A. (2012). Modern Systems Analysis and Design, 6/e. Pearson Education India.

Dennis, A., Wixom, B. H., & Tegarden, D. (2015). Systems analysis and design: An object-oriented approach with UML. John wiley & sons. 

Nooteboom, B. (2008). Interfirm alliances: International analysis and design. Routledge. 

Mahalakshmi, M., & Sundararajan, M. (2013). Traditional SDLC Vs Scrum Methodology–A Comparative Study. International Journal of Emerging Technology and Advanced Engineering, 3(6), 192-196. 

Bricaud, P. (2012). Reuse methodology manual: for system-on-a-chip designs. Springer Science & Business Media. 

Thakurta, R. (2013). Impact of Scope Creep on Software Project Quality. Vilakshan: The XIMB Journal of Management, 10(1). 

Mahadevan, L., Kettinger, W. J., & Meservy, T. O. (2015). Running on Hybrid: Control Changes when Introducing an Agile Methodology in a Traditional" Waterfall" System Development Environment. CAIS, 36, 5. 

Light, M. (2009). How the Waterfall Methodology Adapted and Whistled Past the Graveyard. Gartner Research. 

Edeki, C. (2015). Agile Software Development Methodology. European Journal of Mathematics and Computer Science Vol, 2(1). 

Byrom, L. (2009). Overview of the Waterfall Methodology. Retrieved June, 10, 2011. 

Sutherland, J., Viktorov, A., Blount, J., & Puntikov, N. (2007, January). Distributed scrum: Agile project management with outsourced development teams. In System Sciences, 2007. HICSS 2007. 40th Annual Hawaii International Conference on (pp. 274a-274a). IEEE.