PROBLEM DEFINITION DEFINITION
Those days are gone away when you could easily get seats to park to your vehicle, nowadays with the increase in the population there is an equal increase in the production of the vehicle. Vehicle Vehicle Parking becomes a chance for the people day by day. People face parking problems everywhere, whether it is a theater, local markets, supermarkets, banks, offices, hospitals, marriage halls, railway stations etc. The crowd of the cars, taxies, bikes and other commercial as good as private vehicles made the things worse as never before. There are several issues which are responsible for lack of car park management system these are as follows: •
Their current system s ystem ust allowed to reserve res erve parking through walk!in customers only. "hereas, the operating is during normal business hours. #f customers want to place reserve, they can entirely do so during the operating hours of the business. This
•
implies that the total of parking lot that they can pick up is limited. The next problem is the inability for customer to cover the availability parking. $s the clien clientt is in a hurry hurry and they they bear bear to spen spend d time time to look look for park parkin ing g and and clien clientt experience to go straightly to cover the available parking. %esides, human error might come. &or instance, the staff might be mistaken, which given wrong information about
•
parking. Thirdly, the problem faced by the fund is getting reports of the daily and weekly gross revenue. "ith the current arrangement, the staffs must go through many accounts and gross revenue receipts in order to find a summary of the sales and then produce a story. This procedure is definitely time consuming and once more, there is a possibility of
•
human errors to happen. 'ventually, the business is not able to recogni(e ust which day is the most customer visit. "ith this problem, they are not able to determine which day is the most visit and whether they should govern more from the s supplier for the coming months.
To overcome the issues related to the car park management system problems, effective parking management is required. 'ffective parking management can overcome the troubles related to parking and provide a mixture of strategies and methods to properly employ the state space of parking areas, handling the system, advanced parking facility and improved improved parking design.
%enefits of effective parking management:
There are many benefits of effective parking management. )ome of them are discussed as follows: *inimi(ing risk of human error: +enerally people in a hurry forget to pen down the proper details and the human error may come about. "ith the accessibility of the new developed system, there will be a minimum risk of the human error whereby the detail that needed have to complete given into the system for the system proceed further. Time consuming: Parking management is an effective technique helps to reduce customer to spend time looking for parking, whereas it provide a system whereby clients can book their parking from the place they are to avoid stuck in crowded areas for looking parking and time delay. eview of gross revenue: #n the new scheme, it provides daily, weekly and monthly report to permit the management to cover their profit and to enshroud the most clients visiting days. 'ffective Parking facilities: The car park management companies providing parking facilities and helping to overcome parking related issues at affordable cost. These also help companies staff or frequent visitor to the place to reserve a parking management system for monthly, weekly, daily and hourly to enoy the price reduction. *aximum )ecurity: The parking management systems fitted with advanced monitoring systems that are applied to secure the maximum security of vehicles in the parking lot.
METHODOLOGY (Shamly A/P Sithiaselan) TP!"#$%" Waterfall model
The waterfall model is a sequential design process, used in software development processes, in which progress is viewed as flowing steadily down -like a waterfall through the stages of conception, initiation, analysis, design, building, testing, production/implementation and upkeep. The waterfall development model originates in the fabrication and construction industries: highly structured physical environments in which after!the!fact changes are prohibitively costly, if not inconceivable. )ince no formal software development methodologies existed at the time, this hardware!oriented model was only adapted for software development.
Spiral development
The spiral model combines the idea of iterative development with the system, controlled aspects of the waterfall model. )piral model is a combination of iterative development process model and sequential linear development model i.e. "aterfall model with very high stress on risk analysis. #t allows for incremental releases of the product, or incremental refinement through each iteration around the spiral -$non., 0123.
Ra&i' a&&liatin 'e*el&ment
apid application development -$4 is a software development methodology that uses minimal planning in favor of rapid prototyping. $ paradigm is a working model that is functionally equivalent to a portion of the product. #n the $4 model the functional modules are prepared in parallel as prototypes and are integrated to reali(e the perfect product for quicker product delivery. )ince there is no detailed preplanning, it builds it easier to integrate the modifications within the maturation procedure. $4 proects follow iterative and incremental model and own small teams comprising of developers, land experts, client representatives and other #T resources working progressively on their part or prototype -$non., 0123.
A+ile 'e*el&ment
$gile programming is an advance to proect management, typically employed in software evolution. #t helps teams react to the instability of building software through incremental, iterative work cycles, known as sprints. %ut before turning our discussion to the details of agile programming, it5s best to begin at the beginning with the proect management paradigm that preceded it: waterfall, or traditional sequential development -$non., 0123.
A+ile *s ,ate-.all
$gile provides an incredibly flexible design model, promoting adaptive planning and evolutionary growth. $gile might be identified as a &reeform software design. )oftware developers turn on small modules at a time. 6ustomer feedback occurs simultaneously with growth, as does software testing -for more information about software testing, take a expression at this software testing course. This takes in a number of advantages, especially in proect environments where development needs to be capable to react to changes in requirements rapidly and effectively. $gile can be particularly good in situations where the end!goals of the proects are not distinctly delineated. The client5s requirements will likely gradually clarify as the proect progresses, and development can easily be adusted to meet these new, evolving requirements. $gile is also an excellent option for experimental software design. 7astly, this method also facilitates interaction and communication 8 collaboration is more significant here than design. %ecause interaction among different designers and stakeholders is key, it is especially conducive to teamwork oriented environments. 7ikewise, the emphasis of "aterfall is the proect plan and therefore before beginning any kind of development in that location needs to be a clear plan and a clear vision in order. %ecause the "aterfall method requires upfront, extensive planning, you can launch software fairly quickly. 9ou can also estimate timetables and budgets more accurately, which definitely tends to delight customers.
&urthermore, "aterfall development processes tend to be more secure because they are so plan oriented. &or instance, if a designer drops out of the proect, it isn5t a huge problem, as the "aterfall method requires extensive preparation and support. $ new designer can easily take the old designer5s place, following the development plan without a problem -*ikoluk, 012.
Agile methodology
The methodology that # would wish to choose is agile methodology. The aim of this methodology is for prevention of known problems f rom occurring. "hereby we can be mindful of the problem earlier rather than get involved in problem once proect completion. 7ikewise, agile allow us to know about future problems, and be capable to respond in time. This gets the proect developer easy whereby the plan can be change according to the current state of affairs at the time without any trouble. These are agile principle: •
;ur highest priority is to satisfy the customer through early and continuous delivery of
•
valuable software. "elcome changing requirements, even late in development. $gile processes harness
•
change for the customer
•
a preference to the shorter timescale. %usiness people and developers must work together daily throughout the proect. %uild proects around motivated individuals. +ive them the environment and support
•
they need, and trust them to get the ob done. The most efficient and effective method of conveying information to and within a
•
development team is face!to!face conversation. "orking software is the primary measure of progress.
•
•
• • • •
$gile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. 6ontinuous attention to technical excellence and good design enhances agility. )implicity!!the art of maximi(ing the amount of work not done!!is essential. The best architectures, requirements, and designs emerge from self!organi(ing teams. $t regular intervals, the team reflects on how to become more effective, then tunes and adusts its behavior accordingly.
The reason # choose agile methodology is because of lower risk of proect failure. )mall incremental releases made visible to the product owner and the product team through its development help to key out any issues ahead of time and make it easier to react to change. $lso, by using agile methodology in the proect, it time consuming whereby we can alter the plan according to the situation without any problem. %esides, the quality of agile methodology. $ central rule of agile development is that testing is mixed throughout the lifecycle, enabling regular inspection of the working product as it evolves. This leaves the product owner to make adustments if necessary and contributes the product team early sight of any quality issues. $gile methodology allows developer to cost control. The above approach of fixed timescales and evolving requirements enables a set budget. The scope of the product and its characteristics are variable, rather than the price. #n the end, it registers the business engagement and client satisfaction. The active involvement of a user representative and/or product owner, the high visibility of the product and progress, and the flexibility to change when change is required, create much better business engagement and client satisfaction. Tools and techniques
$gile proect management is an iterative method of defining requirements for engineering and information technology development tasks in a highly flexible and interactive mode, for example agile software development. #t requires empowered individuals from the relevant business, with supplier and customer input. = $gile techniques are best employed in minor proects or on elements of a broader program of work, or on proects that are too complex for the customer to see and set before testing prototypes.>
$gile Proect *anagement #n other words, what we call $gile, is a great way of managing the software development in a process that is highly flexible and that requires empowered individuals that would drive this process successfully. #n my experience # could understand that $gile won5t work properly if one of the following have!not been satisfied:
•
• • • •
$ true collaboration between all the stakeholders -users, developers, testers, handlers, etc.. 6ommon agreement on the process and common destinations 4edication "illingness to share knowledge and expertise with others ;penness
Proect *anagement *ethodologies/&rameworks #n that respect are different methodologies when it gets to the agile process definition itself. $piece of the methodologies, or frameworks is pretty much similar as it calls for the iterative procedure, but on the other side each methodology has its own particularities. 'xamples of agile software proect management frameworks -or methodologies: •
)crum is an iterative and incremental agile software development method for handling
•
software proects and product or application development 'xtreme Programming -?P is a software development methodology which is destined to better software quality and responsiveness to varying client demands. $s a type of agile software development, it advocates frequent @releases> in short development cycles
-timeboxing, which is meant to better productivity and introduce checkpoints where new •
customer demands can be taken up. Aanban is a method for growing software products and processes with an emphasis on ust!in!time delivery while not overloading the software developers. #t emphasi(es that developers pull work from a queue, and the process, from the definition of a task to its delivery to the customer, is displayed for participants to attend.
References Anon., 2015. Agile Programming. [Online] Available at: http://agileprogramming.org/ [Accesse 2! "#$% 2015]. Anon., 2015. SDLC - RAD Model. [Online] Available at: http://&&&.t'torialspoint.com/slc/slc(ra(moel.htm [Accesse 2! "#$% 2015]. Anon., 2015. SDLC - Spiral Model. [Online] Available at: http://&&&.t'torialspoint.com/slc/slc(spiral(moel.htm [Accesse 2) "#$% 2015].
Anon., 2015. Wikipedia. [Online] Available at: https://en.&i*ipeia.org/&i*i/+piral(moel [Accesse 2) "#$% 2015]. i*ol'*, -., 201. Udemy blog. [Online] Available at: https://blog.'em.com/agilevs&aterfall/ [Accesse 2! "'l 2015].
