MAKEUP ASSIGNMENT SIDHARATH - 200802036

Q1 )

a) Seeing the software required , ITERATIVE METHOD is most suited for it :

START

REQUIREMENTS GATHERING AND ANALYSIS

SYSTEM DESIGN

FINISH

REVIEW Feedbacks/testing
IMPLEMENTATION

ITERATIVE MODEL

REQUIREMENTS AND GATHERING : Bestfit Inc wants a good and flexible software , a dynamic one , so first the software should have a price grabbing technique . It should go various online stores which are hot spot for customers and should check prices of each product being sold . It should also check for other offers being given during festivals. Then after surfing throughout internet . It should arrange them in order and see the wide range of prices on a particular product and compare it with their prices and modify them accordingly. The software must be completed within 2 months. Requirements gathering including the platform (the language) on which construction need to be done. As the prices also keep on changing . So , the price grabber has to check again and again on net. .The automated system should be able to fix the price of its product minimum but should be more than 7.5% higher than initial cost price. SYSTEM DESIGN : It includes formation of price grabber tool , other components off the shelf (COTS) , formation of web portal having a dynamic display , which surely attracts customers . All the team members should agree to the design of system . we will keep the iterative model as after reviewing there are chances of changing after final review . So , the design must be little loose such that there can be easy changes after review. So , not freezing is the option we apply on system design . We can add or remove some items from design , after checking whether it is compatible with or not . That is one more reason for using iterative model . Team members also selects the technology required to carry out this task in an easy and quick way . They should think for database related

technology like SQL , and web interface related technology JAVA ,C , etc . Working with language with which they are in familiarity and are expertise is surely the best way to go. Otherwise choosing any random or new language , could cause incomplete project before time. Time allotted to this should be near around 10 days for this all designing. IMPLEMENTATION : As all members are ready to work on agreed Model , they start coding and prepare this model within 1 month . Implementation includes attaching all the components at right places and fully functional final work. Team members of of 8 are working on their respective components and working throughout the day . the other two are still thinking on system design and whether any change they want to make in its construction. Checking other team members how work is going on , anyone need any help or any kind of problem. Imagining how the output looks like and deciding something more to add till the construction adds . There can be chances of coming to new conclusion at any time. So, any kind of emergency STOP within the process . REVIEW : It includes testing of the constructed tool . We update the web portal and allow the customers to come and see what happens . Then taking feedback from the customer and using personal views of team members , we see what can more be modified or what can more be added to design as they still have 20 more days for final launching . S , till then seeing its disadvantages and faults we go for another cycle which includes some more construction to make it better , this is generally called incremental prototyping . As we have again collected all the requirements for further suit we again go for system design . System design included independent components , so changing or removing anything should be done within 20 days . There can be some fresh start in some components of automated system . There is successive approximation again and again to make system better and better . After again reviewing there can be more cycle if time is left . And this can go on till they are fully satisfied with the final model . As the later changes are not great and time consuming as compared to the first cycle so all of them can work at a single time on the new construction which takes an all over less time . So , in a limited time also they can make more and more changes easily . Similar test and more addition are made to test cases as to check whether it is working well on previous test cases and also on the new ones . Finally it is deployed .

New requirements

Imagining and random abstract ideas

REQUIREMENT GATHERING

final changes in DESIGN

What to be included and what not PREVIOUS feedback and limitation (DRAWBACKS RMOVAL)

Any kind of random change incorporated

Previous design

SYSTEM DESIGN

final design after agreement

SUGGESTION OR ANY EMERGENCY STOP

If design was not as expected / keep Iterating it here and here until

done

IMPLEMENTATION PREVIOUS DESIGN

Output as degined/ expected

READY FOR TESTING/TESTING

DEPLOYMENT

NEXT CYCLE CONSTRUCTION DONE YET !! REVIEWING

FAULTS AND FEEDBACKS

Cycles after cycle , it keeps on iterating , a As after successive cycle model gets better and better with feedbacks and new ideas so sense of satisfaction also increases with each iteration . This continues till time is all out . Finally ready for deployment .

Q2 )
FUNCTIONAL REQUIREMENTS The automated system should have price grabbing tool : NFR -a) price grabber tool should take a reasonable amount of time to check on net for other items. b) Should be quick and to the point in taking data from other sites WEB portal must provide customers option to compare prices of different items : NFR associated : a) web interface must be attractive b) it should be dynamic , not static and boring c) It should be easily accessible even at slow internet speed . d) Good searching procedure to have access to wide variety of products. e) 24h hour availability and responding f) quick to learn Special registration facility for some users who want to become permanent member a) It should keep profile of registered user secure and private b) Special discounts to regular trusted users c) Early information exchange with permanent customers about new products d) maintain early records and database of permanent users WEB PORTAL must keep updating prices , keeping in mind the profit margin of 7.5 % regularly NFR - a) Profit should be as maximum as possible keeping in mind other market prices b) It should be quick in fixing prices
FEEDBACK MECHANISM AND TIME TO UPGRADING RATINGAVAILABLE OF PRODUCTS BEING SOLD AVAILABILTY OF CREDIT CARD/DEBIT CARD ACCEPTANCE

NFR -- a) Secure and fast payment over the portal

System and design should allow changes , there should not be rigidness in it System specification must be verifiable, unambiguous, complete and correct at the least System specification must be tolerant of incompleteness and augmentable

LOGIN USER

Status of current order

Browsing and add to cart

Cancel order

ADD/remove from cart (shopping)

Payment option Account details

Q3) Client server architecture As many people can have access to the same machine at the same time two tier architecture or client server architecture is best . Therefore there are only two components CLIENT and SERVER because clients working on their personal machine and the website server and web portal server are only two places encapsulating all processes and data in this architecture . These are entities shown in rectangular box in the following diagram . These fill are criteria of being components i.e providing application specific services , restricting access through clearly defining interfaces . Server do not know number of identities of clients . But clients know servers identity . The connectors involved are RPC(remote procedure call) protocols .All the control flow , data movement is done by RPCs and also transactions . In this type of communication , information is exchanged between two processes and using functionality which is on different process (invoking functionality residing in another process). The two tier architecture provides usability , scalability , and flexibility of applications . this architecture have user friendly interface . Clients send queries or data through internet . The data in form of procedure calls interact with Web Server directly . The data changed fed to web portal are stored and processed in the server . Any more in return information is sent via RPC again to clients , if any .

WEB PORTAL

PRICE GRABBER

INTERNET
SERVER

CLIENT 1

CLIENT 2 DATABASE

CLIENT 3

CLIENT 1

CLIENT 2

CLIENT 3

PROCEDURE CALL

PROCEDURE CALL

PROCEDURE CALL

SERVER

Q8 ) SDLC - Sometimes software development gets too complicated that it gets out of reach of implementation. or too abstract that it becomes difficult to give a design of it . Software development field can be accessed only when the user has proper skill obtained from lot of experience. Even after deciding, thinking and having feedback about the project, there is not surety of it definitely becoming a success. The stuff written on paper is usually not the one got in reality, the Practical piece of software got through so many cycles and efforts remains at a distance from the original. People generally have different ideas of creating things, but in SDLC everyone has to go for a particular fixed pattern. This puts a limitation on users to create as required not through their own way. This puts a lot of psychological pressure on users to go on a fixed path rather using their own free will and intuition. If user moves out with his free will then there is no need of documentation, then it is also not likely that end results would meet. Everyone will go in their own direction and project might be a failure. Sometimes too much complexity of codes might give problem in properly executing it , single bug can stop the whole project . If it is not properly detectable, then that is a greater problem. It requires working to exhaustible time , which becomes little inhuman sometimes . There is never a surety of project becoming a huge success in practical even if appeared to be on paper or before designing. It depends on hands of person to bring out its originality. Numerous testing never gives surety that it is working ok , as you cant create that much complex and large test cases . Communication is also a skill needed to carry out work efficiently , it may be so abstract that visualizer cant demonstrate or explain it to anyone. Overall it can create Headache . It is work which requires total interest and dedication , little slanginess can lead to disinterest in this field and finally quitting . Long time skill is one of the foremost requirement before entering this field . Good communication so that you could make your ideas totally real by expressing in such a way that it makes everyone feel how it would look like . Avoiding too much complexity initially definitely brings success though in a slow way. Making yourself adapted to long time working hours can help . Better

visualization is necessary to give a direction to the flow of project . So , team leaders should have this talent in them . Following SDLC previously specified might not work as it creates stiffness of mind all the time. Q9) The purpose of re submission is definitely improvement in grades. Q7) We have divided our architecture as 2 tier architecture . The design pattern most suited for this is mvc (model-viewcontroller architecture). MVC is generally used while developing online shopping services. User interfaces keep on changing over net where good looks and attractiveness matter a lot and is a competitive concern . Now separate the concerns into MODEL , VIEW , CONTROLLER . MODEL keeps the original data and information VIEW handles presenting of data as it can be done in many ways CONTROLLER takes input from user and asks permission from MODEL to change presentation on the VIEW.

CONTROLLER

USER

MODEL

VIEW

These are independent concerns. Changing any of these doesnt lay effect on the other. The MODEL doesnt need change internal applications . Presentation views ar never mixed with permanent applications as presentations keep changing . Security can come in this way as everything is independent of each other so changing anything doesnt lay any effect on any other thing.

Q6) scenario: When given website is inactive somehow 1) click on the url to open it . When given order is out of stock 1) Port should reveal as Out of stock 2) should notify the user when it becomes available 3) should bring him to previous page without changing any of the contents of his balance and cart. Browser compatibility : Check whether the look and feel of the web page contents , designs , etc are similar through various browsers. Error for typing wrong items which doesnt exist How much load the portal can handle at a single time , when various users try to access it. Security : Unauthorized users are not allowed to log in . When Payment options are not working : Portal should not go for any kind of transaction of money if there are faults from behind or there is no connectivity with bank . It should allow to switch on to new payment options if one is not working .

Q5) GUI features : GUI should have advertisement panel to show what is recently out and what new customer services have been added to it . If they are regular customers then sending them mail and telling them the new discount or offers being given . GUI language should be user friendly and understandable to all people browsing the contents of site . There are either videos going on related to ads on portal or some king of pamphlet . So , generally users browse them randomly often lead to mistakes. So ,providing emergency leave is also provided. Error checking should be there , there should be total elimination of part of code which Can lead to hang or any dead point or fatal error .

As portal is use friendly it should be handy to use , So provide such buttons and pathways that user has to keep low memory regarding items. Dialogue written or shown must be precise and relevant to the product or offer , nothing extra or elaborated . Headings must be there clearly visible , such that user gets to know for sure to what it is related to , and the whole document related to it must be behind the link given .(It should be a hyperlink). Front pages should not be too messy . ONLINE BANKING / CREDIT CARD / DEBIT CARD

SIGN OUT

Q4)
shopping LOGIN Cancel order USER PAYMENT

View status

FEEDBACK

Manage membership LOGIN POST NEWS/EVENTS SIGN OUT MANAGE BANK ACCOUNT MANAGER FEEDBACK READ BROKEN LINKS

ACTORS playing role in use case diagrams are new users , registered users and manager . NEW USER USERNAME - ******* PASSWORD - ******* SIGN IN

LOGOUT

LOGIN CUSTOMER

SHOPPING CART

PLACE ORDER

VERIFICATION

PAYMENT OPTIONS ORDER CONFIRM READY FOR SHOPPING EMAIL SENT

Message sent SMS