The NextGen POS System

NextGen POS System… • P-O-S is a Point-of-Sales System. • What is the target of the Sales in General? • More People Checks into the mall=MORE MONEY… .

• Would the Prefer the Same Mall again??? • They Wouldn’t…So.. . 100 people checked into a mall and only 20 people got out quickly but other 80 stuck at cashier counter because……….in point of sales we design a system. • Cashier wasn’t able to send them out due to machine malfunction.-Let us take an Example of Cashier Check out Sales Let us assume In an Instance....

inventory management and health care. • POS terminals have transcended several industries like hospitality. . extending its application from simple transaction machines at the checkout counter in a provision store.• Point-of-sales (POS) terminals have played a very critical role in the evolution of the retail sales industry. • Automated transactions have decreased customer waiting time at the cash counter and increased customer value for the retailer.

*Advanced POS machine .• A Simple POS Machine.

Architectural layers of a Common POS Machine • A typical object-oriented information system is designed in terms of several architectural layers or subsystems The following is not a complete list. . a software class named Sale) that fulfill application requirements. but provides an example: • User Interface— graphical interface. • Technical Services— general purpose objects and subsystems that provide supporting technical services. such as interfacing with a database or error logging. windows. • Application Logic and Domain Objects— software objects representing domain concepts (for example. These services are usually application-independent and reusable across several systems.

Next GEN POS State Machine Diagram .

INCEPTION .

• It will include analysis of perhaps 10% of the use cases.So…Inception is. .. vision. and business case. • • Inception in one Sentence: Envision the product scope. analysis of the critical non-Functional requirement. • Inception is the initial short step to establish a common vision and basic scope for the Project. creation of a business case. and preparation of the development Environment so that programming can start in the elaboration phase.

it makes a good context diagram that is. what lies outside of it. showing the boundary of a system. It serves as a communication tool that summarizes the behavior of a system and its actors . and how it gets used.login withdraw deposit balance checking customer admin layout generate report maintain atm maintain db A use case diagram is an excellent picture of the system context.

clarifies most requirements. • In the UP.. . and tackles the high-risk issues. Therefore. • Elaboration follows Inception… • Now what is Elaboration? • Elaboration is the initial series of iterations during which the team does serious investigation. implements (programs and tests) the core architecture. "risk" includes business value. early work may include implementing scenarios that are deemed important. but are not especially technically risky.Elaboration.

Tasks Performed in Elaboration • the core. risky software architecture is programmed and tested • the majority of requirements are discovered and stabilized • the major risks are mitigated or retired .

users. developers • write most of the use cases and other requirements in detail. once per elaboration iteration . often. implement. through a series of workshops.Key Ideas and Best Practices in Elaboration • do short time boxed risk-driven iterations • start programming early • adaptively design. realistically • adapt based on feedback from tests. and test the core and risky parts of the architecture • test early.