|
Template
Product Management
In the field of Product Management, we first review your
business environment, your product and service offerings in a SWOT review
(strengths, weaknesses, opportunities, threats). With a solid
understanding of your business, we then develop detailed designs for new,
distinguishing solutions based on customer-driven innovative
strategy and market demand. We develop the business solutions based
on analyses of process and functionality requirements. We review your
target markets, their stakeholders and end-users and
determine an overall product or information system. We
elaborate your own strategy scheme and use it to increase sales
or efficiencies per business requirements. We can measure
the benefits of the new product or information system in terms of
financial performance, such as improved earnings per share or increased
revenues, items that are directly caused by a new information
solution. We can drill into detailed designs in
preparation for development.
Product Design and
Prototyping-
the link, above, takes you to an early version of a Contact
Management application. You might think of this prototype as the simplest CRM
application in the world. From a simple prototype like this, we can
develop increasingly more detailed and sophisticated capabilities that respond
to the requirements of the business process.
The next version of
Contact Management Application-
the link, above, takes you to a slightly more developed
version of the Contact Management application indicated above. You might
think of this version as an incremental step in developing a CRM
application in a product life cycle. From a simple prototype, we develop
increasingly more detailed and sophisticated capabilities that respond to the
requirements of the business processes. For
example, from marketing operations to sales and on to customer
services at the front-end of demand chain management. At the
back-end, the supply chain management, we can develop information systems
that respond to the requirements to manage all types of logisitcs and
transactions needed to procure products.
This simple application enables sales and account managers to
document who their contacts are and how they are staying in touch with them in
order to maintain a memory of the account for new or repeat sales and
services.
This simple application builds on object oriented programming by
using a separate set of software components, classes, between the SQL
database, a middle-ware layer of data management components, and the
presentational, client layer. This illustrates a miniature n-tier
architecture. The "n-tier" structure enables one to break down an
otherwise very large enterprise information system into smaller components in
order to obtain the benefits of interchangability, reusability, flexibility,
and scalability.
Event Scheduling
and Contact Calendar Application-
the link, above, takes you to an application that
complements the Contact Management application indicated above. You might
think of this applicaton as an additional set
of capabilities in developing a full CRM application suite. This
application enables the end-user to name, describe and date an event, for
example, a meeting, a seminar, a conference and to manage that event by date
and time as well as by any recurrences.
This application reuses some of the classes in the previous
application such as the database access class, the business rules as well
as the validation class and adds to these a calendar event management
class.
ECommerce - Selling products
online - -
The link, above, takes you to a prototype version of an ECommerce
application, for which we provide example requirements documents at the link
below. Much like buying from "Barnes and Noble.com," for example, this
prototype application is designed particularly to enable
restaurant managers to purchase fresh ingredients online for prompt
delivery retailers or warehouse dealers of food products.
Prototyping is only one of many elements in the overall requirements
process. Software prototyping enables all stakeholders of the solution to
see a tangible example of their goal. It serves as a first stake in
the ground for setting the foundation and moving on in developing the
requirements. Prototypes brings use-cases to life and closes some of the
gaps stakeholders have in understanding the business solutions and their
requirements. It also serves as a starting point to stimulate discussions
and feedback for the solution agreeable to all stakeholders. In this way,
it serves as an important step in moving the solution process foreward while
lowering the risks of dissatisfied users. Yet, it is only one of many
elements in the requirements process.
We use this particular "ECommerce" application as an example to develop an
entire set of documentation that we can use to establish the goals, design, and
requirements for any software application. The methodology we use in
this case is one that is widely accepted and popular in the software industry:
UML (unified modeling language). Organizations such as IEEE have
recognized this methodolgy as a form of best practices for increasing
productivity in software development projects, greatly reducing costs and
increasing quality.
As you may find on the page linked below, the types of
documents listed below, follow a standard process in software lifecycle
projects:
-
Business Purpose, Discovering the Business, Business Vision
-
Use Cases and Business Requirements
-
Unified Process - Gathering Business Requirements
-
Specifications
-
Various types of diagrams and charts
-
Agreeing on the Solution and the Design
-
Project plan
-
Professional Services Process
-
End-user review, testing, implementations
-
Happy Clients -- Solutions well designed per the
requirements
Software
Requirements Process - Using the Unified Process, we provide a
practical example analysis of the ECommerce application linked
above.
As you can see, this website takes advantage of globalization.
When globalizing your website or software products, it is important to plan and
budget for the resources required to maintain the system in multiple
languages. For exsample, as consultants, we do not have the time to
maintain the same version of the website in all four of the languages that we
chose. English remains the principle version of the website while the
other language versions are updated and revised only occaisionally. The
following two links demonstrate the ability of Unicode to support almost any
spoken language in the world:
Globalization
- Localization of Software Solutions
Unicode support of hundreds of Languages
More to come....
Soon, to demonstrate more of our work and capabilities, we are
adding more presentations to this website.
Does this interest you? Then we should talk soon. Send me an email(mailto:mbiskeborn@hotmail.com)
or call me: 1-949-293-2016.
I look foward to your call soon...
Send me E-Mail (mbiskeborn@hotmail.com) or send comments or questions through
the Website:Input form
Thank you!
|