Abstract: Systems and methods for transforming data for a batch-based legacy software program into data suitable for processing by a streaming-based new software program. In some aspects, the system generates an information stream for multiple threads from batch information received from the legacy software program. The system processes the information stream for the multiple threads using the new software program. If there is a mismatch between outputs of the legacy and new software programs for at least one thread, the system adjusts a data model of the new software program to address the mismatch and generates an updated information stream for processing by the new software program.

Abstract: Systems and methods for transforming data for a batch-based legacy software program into data suitable for processing by a streaming-based new software program. In some aspects, the system generates an information stream for multiple threads from batch information received from the legacy software program. The system processes the information stream for the multiple threads using the new software program. If there is a mismatch between outputs of the legacy and new software programs for at least one thread, the system adjusts a data model of the new software program to address the mismatch and generates an updated information stream for processing by the new software program.

Abstract: A method and system are disclosed for behavioral analysis for profiling wireless subscribers. The method includes loading carrier reference data comprising a set of common categories and loading a plurality of behavior records of at least two types, wherein each behavior record is generated by a mobile device activity of a subscriber. The method proceeds by associating each behavior record with one or more of the categories, thereby generating categorized data records. Finally each category associated with a behavior record is added to a subscriber profile for the subscriber whose activity generated the behavior record.

Abstract: A method of test integration for early application development is provided. The method comprises defining a business case, identifying a plurality of systems to enable the business case, identifying at least one control document including handshakes for the systems, and generating test cases for each of the systems, the test cases including the handshakes useful to test applications. A testing integration system for early application development is also provided. The system comprises an input module operable to permit selection of a plurality of systems defining a business case, a control document defining handshakes between the systems, a template operable to receive information related to the control document and further operable for arranging the systems to enable the business case, and a generator operable to generate test cases including the handshakes based on the arrangement of the systems in the template.

Abstract: A system and method are provided for modeling functional requirements for a project. The method includes creating a first model for a first project, categorizing a portion of the first model according to an eTOM area related to the first project, storing the first model in a repository according to the eTOM category, searching the repository for a model for a project categorized by an eTOM area similar to an eTOM area associated with a second project, and when a similar model is found, using the similar model as a basis for creation of a second model for the second project.

Abstract: A system for automatically counting function points is provided. The system includes an electronic document, an analysis component, and a user interface. The electronic document contains a sequence diagram that specifies interactions in a software application. The analysis component can analyze the interactions in the sequence diagram to identify a start point and an end point in the sequence diagram as a function point. The analysis component can also maintain a count of the function points. The user interface can promote counting one or more function points when more than one of the sequence diagrams involve data that is part of a set of data objects identified via the user interface.

Abstract: A system and method for engineering data into interface control documents is provided. The method includes creating and loading an interface control document by selecting features of an interface control document to create, providing a standards document having interface control document standards, and providing a case tool for maintaining interface control documents. The method provides for generating the interface control document using the standards document and based upon the selected features, and storing the interface control document in the case tool. The method includes designating a document having data attributes for the interface control document, reading at least some of the data attributes from the document, loading at least some of the data attributes read from the document into the interface control document, and storing the interface control document having at least some of the data attributed in the case tool.

Abstract: A system for managing and monitoring a project to be developed is provided. The system includes a first and a second document, the first document identifies a first set of interactions between a plurality of applications. The first set of interactions identifies functionality of the project to be developed. The second document identifies a second set of interactions within at least one of the applications. The second set of interactions identifies additional functionality of the project. The system also includes a baseline document and an estimator component. The baseline document identifies existing functions of interactions between the applications and existing functions of interactions within applications. The estimator component is operable to access the first, second, and baseline document and to count a number of interactions identified in the first and second sets of interactions not identified in the baseline document of existing functions of interactions.

Abstract: A system for building software use cases and related state diagrams based on a model of business activities is provided. The system comprises the model of business activities and a computer based modeling tool that is used to compose the use cases and the related state diagrams. The system includes an integration component, which maps the business activities to use cases, and a graphical user interface, which illustrates the relationships among use cases and the relationships between use cases and business requirements. A state diagram component maps business activities to assist in the preparation of state activity diagrams. The model of business activities enumerates business activities and associates each business activity with the business domain in which the business activity is normally conducted. The integration component provides a list of selectable business activities to the graphical user interface from which to compose use cases and state activity diagrams.

Abstract: A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool for analyzing calls, contained in the constructed model, between applications of the integrated enterprise and a database shared thereby. The call analysis tool identifies data attribute imbalances in calls between the applications of the integrated enterprise and the shared database. Data attribute imbalances result if the calls attempt to consume data which was never produced or if the calls produce data which is never consumed. The call analysis tool also generates producer/consumer maps of the data attributes used in the model, producer exception reports which identify data attributes which are consumed but never produced and consumer exception reports which identify data attributes which are produced but never consumed.

Abstract: A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool which validates compliance of documents constructed by the first tool with a set of standards. The documents which may be constructed by the first tool include an analysis interface control document (“ICD”) and a design ICD document. The second tool may then be used to selectively compare either the analysis ICD or the design ICD with selected ICD standards and generate an analysis ICD document standards exception report and a design ICD document standards exception report, respectively, which lists each variation of the analysis and design ICD documents from the selected ICD standards. The analysis and/or design ICD standards exception reports may subsequently be used as guides to correct errors in the analysis and/or design ICD documents causing the exceptions.

Abstract: A selected scenario of a design ICD document for an integrated enterprise is validated by examining each IDL call of each sequence diagram forming part of the selected scenario. A list of data attributes contained in one or more of the IDL calls are generated and each IDL call associated therewith is generated. A physical location to which each such IDL call is mapped is then associated with the IDL call. By analyzing the IDL calls and associated physical locations on a data attribute-by-data attribute basis, inconsistencies in the physical mapping of the data attributes to the databases forming an IIS for the integrated enterprise may be identified and subsequently corrected.

Abstract: A device for modeling an integrated enterprise includes a first tool for constructing a model of the integrated enterprise and a second tool for analyzing inter-application call sets contained in the constructed model. The second tool analyzes a selected inter-application call set by constructing a data attribute matrix having a row for each data attribute contained in at least one of the inter-application calls and a column for each one of the inter-application calls. The data attribute matrix is then marked to indicate which ones of the data attributes are contained in which ones of the selected inter-application calls. The constructed data attribute matrix may then be analyzed to identify improper association of data attributes with calls.