| This thesis explores whole software developing process of a billing system in telecommunication field, summarizes factors that affect the quality of software products and methods that improve efficiency in the process of development. This billing system is able of not only handling the billing information for specific services chosen by customers but also extending to receive billing information transferred from other billing systems. This system can integrate customer information for data mining to serve customer characteristically.As most of developers realized, coding shall not be the primary problem in the process of development, contrarily, requirement analysis and frame design need to be emphasized particularly on, because both requirement analysis and frame design are really keys to shape software produce. The failures of lots of software products are resulted in ignoring the importance of requirement analysis and put overmuch emphasis on coding. Therefore, based on requirement analysis and frame design for this billing system, acknowledge and experience in similar projects, I summarized potential problems to extreme extend which might lead to unexpected result in following development process. In this billing system, using some UML tools and design method to describe the system and formed a well extensive and strong product. At the same time good coding technology can improve the efficiency of the product, in this system used many design pattern like Factory pattern, Singleton pattern, Proxy pattern and other design pattern, besides of this design patter also use some other technology like database connection pool. All this can provide system most reusable and security.During requirement analysis phase, formed requirement document and use Rational Rose UML tools to describe the requirement of customer. The phase designed the functions of system. But most difficulty is to describe the requirement accurately, which include object-oriented, object-computer and other interface. During this step any mistake will cause problem in the future, modification will also become difficult. This results maybe caused by customers who are not ensure the requirement what they want. Requirement analysis should think of the change of the user requirement. During item development there are four problems should be noticed: limited resource of requirement, mistiness define of requirement, CPD trap and NV trap.Requirement is not easily defined, which requests fully think about the risk during make requirement analysis. Some reasons maybe cause this risk, they are: not enough customer, continuously added customer requirement, mistiness requirement, needless requirement, excessively easy requirement, ignore different class of customer, inaccurate plan. A good requirement should be: clear, integrated, consistent, fathomable, during this phase also introduce a complete process of make requirement.During structure design phase, the system adopt MVC (Module-Controller-View) pattern, which is a classic design pattern. User request service through View layer, which formed an event, this event is passed to Controller layer, which judges what should be done and then passed to Model layer, Model layer process the request and return the result to the customer. During structure design, use UML tools, Rational Rose, drawing the status and sequence of the key process. The following step is to fill the structure with design pattern. A well designed structure frame is based on many simple defined design modes. At the same time the well designed pattern could help you understand the system better. At present distributed product development mostly use EJB component technology of J2EE frame, while in this item development non-distributed mode is adopted. During coding phase, analyzes some technology. Data is the core of company business affairs, most operates will use the database, so database connection pool technology will become absolutely necessarily. Continually make connection and disconnection will drop efficie...
|
PDF Full Text Request