information systems management

1、The Design and Development of the Students' Information Management System As information technology advances, various management systems have emerged to change the daily lives of the more coherent, to the extent possible, the use of network resources can be significantly reasonable reduction of

2、manual management inconvenience and waste of time.Accelerating the modernization of the 21st century, the continuous improvement of the scientific and cultural levels, the rapid growth of the number of students will inevitably increase the pressure information management students, the inefficient ma

3、nual retrieval completely incompatible with the community's needs. The Student Information Management Systemis an information management one kind within system, currently information technique continuously of development, the network technique has already been applied in us extensively nearby of

4、 every trade, there is the network technical development, each high schools all make use of a calculator to manage to do to learn, the school is operated by handicraft before of the whole tedious affairs all got fast and solve high-efficiencily, especially student result management the system had in

5、 the school very big function, all can be more convenient, fast for the student and the teacher coming saying and understand accurately with management everyone noodles information. AbstractIt is a very heavy and baldness job of managing a bulky database by manpower. The disadvantage, such as great

6、capacity of work, low efficiency and long period, exist in data inputting, demanding and modification. So the computer management system will bring us a quite change.Because there are so many students in the school, the data of students' information is huge, it makes the management of the inform

7、ation become a complicated and tedious work. This system aims at the school, passing by practically of demand analysis, adopt mighty VB6.0 to develop the student information management system. The whole system design process follow the principle of simple operation, beautiful and vivid interface and

8、 practical request. The student information management system including the function of system management, basic information management, study management, prize and punishment management , print statement and so on. Through the proof of using, the student information management system which this tex

9、t designed can satisfy the school to manage the demand of the aspect to students' information. The thesis introduced the background of development, the functions demanded and the process of design. The thesis mainly explained the point of the system design, the thought of design, the difficult t

10、echnique and the solutions. The student managed the creation of the system to reduce the inconvenience on the manpower consumedly, let the whole student the data management is more science reasonable.The place that this system has most the special features is the backstage database to unify the mana

11、gement to student's information.That system mainly is divided into the system management, student profession management, student file management, school fees management, course management, result management and print the statement.The interface of the system is to make use of the vb software cre

12、ation of, above few molds pieces are all make use of the vb to control a the piece binds to settle of method to carry out the conjunction toward the backstage database, the backstage database probably is divided into following few formses:Professional information form, the charges category form, stu

13、dent the job form, student the information form, political feature form of student, the customer logs on the form The system used Client/Server structure design, the system is in the data from one server and a number of Taiwan formed LAN workstations. Users can check the competence of different syst

14、ems in different users submit personal data, background database you can quickly given the mandate to see to the content.Marks management is a important work of school,the original manual management have many insufficiencies,the reasons that,students' population are multitudinous in school,and e

15、ach student's information are too complex,thus the work load are extremely big,the statistics and the inquiry have been inconvenient.Therefore,how to solve these insufficiencies,let the marks management to be more convenient and quickly,have a higher efficiency,and become a key question. More an

16、d more are also urgent along with school automationthe marks management when science and technology rapid development,therefore is essential to develop the software system of marks register to assist the school teaching management.So that can improve the marks management,enhance the efficiency of ma

17、nagement. Systems Analysis and DesignSystemsWorking under control of a stored program, a computer processes data into information. Think about that definition for a minute. Any given computer application involves at least three components: hardware, software, and data. Merely writing a program

18、isnt enough, because the program is but one component is in a system.A system is a group of components that work together to accomplish an objective. For example, consider a payroll system. Its objective is paying employees. What components are involved? Each day, employees record their hours worked

19、 on time cards. At the end of each week, the time cards are collected and delivered to the computer center, where they are read into a payroll program. As it runs, the program accesses data files. Finally, the paychecks are printed and distributed. For the system to work, people, procedures, input a

20、nd output media, files, hardware, and software must be carefully coordinated. Note that the program is but one component in a system.Systems AnalysisComputer-based systems are developed because people need information. Those people, called users, generally know what is required, but may lack the exp

21、ertise to obtain it. Technical professionals, such as programmers, have the expertise, but may lack training in the users field. To complicate matters, users and programmers often seem to speak different languages, leading to communication problems. A systems analyst is a professional who translates

22、 user needs into technical terms, thus serving as a bridge between users and technical professionals.Like an engineer or an architect, a systems analyst solves problems by combining solid technical skills with insight, imagination, and a touch of art. Generally, the analyst follows a well-defined, m

23、ethodical process that includes at least the following steps:Problem definitionAnalysisDesignImplementationMaintenanceAt the end of each step, results are documented and shared with both the user and the programmers. The idea is to catch and correct errors and misunderstandings as early as possible.

24、 Perhaps the best way to illustrate the process is through example.Picture a small clothing store that purchases merchandise at wholesale, displays this stock, and sells it to customers at retail. On the one hand, too much: stock represents an unnecessary expense. On the other hand, a poor selection

25、 discourages shoppers. Ideally, a balance can be achieved: enough, but not too much.Complicating matters is the fact that inventory is constantly changing, with customer purchases depleting stock, and returns and reorders adding to it. The owner would like to track inventory levels and reorder any g

26、iven item just before the store runs out. For a single item, the task is easy-just count the stock-on-hand. Unfortunately, the store has hundreds of different items, and keeping track of each one is impractical. Perhaps a computer might help.Problem DefinitionThe first step in the systems analysis a

27、nd design process is problem definition. The analysts objective is determining what the user needs. Note that, as the process begins, the user possesses the critical information, and the analyst must listen and learn. Few users are technical experts. Most see the computer as a “magic box,” and are n

28、ot concerned with how it works. At this stage, the analyst has no business even thinking about programs, files, and computer hardware, but must communicate with the user on his or her own terms.The idea is to ensure that both the user and the analyst are thinking about the same thing. Thus, a clear,

29、 written statement expressing the analysts understanding of the problem is essential. The user should review and correct this written statement. The time to catch misunderstandings and oversights is now, before time, money, and effort are wasted.Often, following a preliminary problem definition, the

30、 analyst performs a feasibility study. The study, a brief capsule version of the entire systems analysis and design process, attempts to answer three questions:1.      Can the problem be solved?2.      Can it be solved in the users environment?3.  &#

31、160;   Can it be solved at a reasonable cost?If the answer to any one of these questions is no, the system should not be developed. Given a good problem definition and a positive feasibility study, the analyst can turn to planning and developing a problem solution.AnalysisAs analysis begins, th

32、e analyst understands the problem. The next step is determining what must be done to solve it. The user knows what must be done; during analysis, this knowledge is extracted and formally documented. Most users think in terms of the functions to be performed and the data elements to be manipulated. T

33、he objective is to identify and link these key functions and data elements, yielding a logical system design.Start with the systems basic functions. The key is keeping track of the stock-on-hand for each product in inventory. Inventory changes because customers purchase, exchange, and return product

34、s, so the system will have to process customer transactions. The stores owner wants to selectively look at the inventory level for any product in short supply and, if appropriate, order replacement stock, so the system must be able to communicate with management. Finally, following management author

35、ization, the system should generate a reorder ready to send to a supplier.Given the systems basic functions, the analysts next task is gaining a sense of their logical relation. A good way to start is by describing how data flow between the functions. As the name implies, data flow diagrams are part

36、icularly useful for graphically describing these data flows. Four symbols are used. Data sources and destinations are represented by squares; input data enter the system form a source, and output data flow to a destination. Once in the system, the data are manipulated or changed by processes, repres

37、ented by round-corner rectangles. A process might be a program, a procedure, or anything else that changes or moves data. Data can be held for later processing in data stores, symbolized by open-ended rectangles. A data store might be a disk file, a tape file, a database, written notes, or even a pe

38、rsons memory. Finally, data flow between sources, destinations, processes, and data stores over data flows, which are represented by arrows.Preliminary data flow diagram for the inventory system. Start a CUSTOMER. Transactions flow from a customer into the system, where they are handled by Process t

39、ransaction. A data store, the STOCK, holds data on each item in inventory. Process transaction changes the data to reflect the new transaction. Meanwhile, MANAGEMENT accesses the system through Communicate, evaluating the data in STOCK and, if necessary, requesting a recorder. Once a reorder is auth

40、orized, Generate reorder sends necessary data to the SUPPLIER, who ships the items to the store. Note that, because the reorder represents a change in the inventory level of a particular product or products, it is handled as a transaction.The data flow diagram describes the logical system. The next

41、step is tracing the data flow. Start with the destination SUPPLIER. Reorders flow to suppliers; for example, the store might want 25 pairs of jeans. To fill the order, the supplier needs the product description and the reorder quantity. Where do these data elements come from? Since they are output b

42、y Generate reorder, they must either be input to or generated by this process. Data flow into Generate reorder for STOCK; thus, product and reorder quantities must be stored in STOCK.Other data elements, such as purchased and the purchase quantity, are generated by CUSTOMER. Still others, for exampl

43、e selling price and reorder point, are generated by or needed by MANAGEMENT. The current stock on-hand for a given item is an example of a data element generated by an algorithm in one of the procedures. Step by step, methodically, the analyst identifies the data elements to be input to, stored by,

44、manipulated by, generated by, or output by the system.To keep track of the data elements, the analyst might list each one in a data dictionary. A simple data dictionary can be set up on index cards, but computerized data dictionaries have become increasingly popular. The data dictionary, a collectio

45、n of data describing and defining the data, is useful throughout the systems analysis and design process, and is often used to build a database during the implementation stage. The idea of analysis is to define the systems major functions and data elements methodically. Remember that the objective i

46、s translating user needs into technical terms. Since the system starts with the user, the first step is defining the users needs. Users think in terms of functions and data. They do not visualize programs, or files, or hardware, and during this initial, crucial analysis stage, it is essential that t

47、he analyst think like a user, not like a programmer.Data flow diagrams and data dictionaries are useful tools. They provide a format for recording key information about the proposed system. Also, they jog the analysts memory; for example, if the analyst doesnt have sufficient information to complete

48、 a data dictionary entry, he or she has probably missed something. Perhaps most importantly, the data flow diagram and the data dictionary document the analysts understanding of the system requirements. By reviewing these documents, the user can correct misunderstanding or oversights. Finally, they

49、represent an excellent starting point for the next step, design.DesignAs we enter the design stage, we know what the system must do, and thus can begin thinking about how to do it. The objective is to develop a strategy for solving the problem. At this stage, we are not interested in writing code or

50、 in defining precise data structures; instead, we want to identify, at a black box level, necessary programs, files, procedures, and other components.The data flow diagram defines the systems necessary functions; how might they be implemented? One possibility is writing one program for each process.

51、 Another is combining two or more processes in a single program; there are dozens of alternative solutions. Lets focus on one option and document it.A system flowchart uses symbols to represent programs, procedures, hardware devices, and the other components of a physical system. Our flowchart shows

52、 that transaction data enter the system through a terminal, are stored on an inventory by a data collection program, and then are stored on an inventory file. Eventually, the inventory file is processed by a Report and reorder program. Through it, management manipulates the data and authorizes reord

53、ers.Look at the system flowchart. It identifies several hardware components, including a computer, a disk drive, a data entry terminal, a printer, and a display terminal. Tow programs are needed: Process transaction and Report and reorder. In addition to the hardware and the programs, well need data

54、 structures for the inventory file and for data flows between the I/O devices and the software. Note that system flow chart illustrates one possible solution; a good analyst will develop several feasible alternatives before choosing one.The flowchart maps the system, highlighting its major physical

55、components. Since the data link the components, the next task is defining the data structures. Consider, for example, the inventory file. It contains all the data elements from the data store STOCK. The data elements are listed in the data dictionary. Using them, the files data structure can be plan

56、ned.How should the file be organized? That depends on how it will be accessed. For example, in some applications, data are processed at regular, predictable intervals. Typically, the data are collected over time and processed together, as a batch. If batch processing is acceptable, a sequential file

57、 organization is probably best.It is not always possible to wait until a batch of transactions is collected, however. For example, consider an air defense early warning system. If an unidentified aircraft is spotted, it must be identified immediately; the idea of waiting until 5:00 p. m because “tha

58、ts when the air defense program is run” is absurd. Instead, because of the need for quick response, each transaction must be processed as it occurs. Generally, such transaction processing systems call for direct access file.Our inventory system has tow programs. One processes transactions. A direct

59、access inventory file seems a reasonable choice. The other allows management to study inventory data occasionally; batch processing would certainly do. Should the inventory file be organized sequentially or directly? Faced with such a choice, a good analyst considers both options. One possible system might accept transactions and process them as they occur. As an alternative, sales slips might be collected throughout the day and programs would deal with direct access files; in the second system, they would be linked to sequential files. A program to pr