#run program

Realistically, Vader should have destroyed the two programs that housed his Jedi Master’s memories as soon as he had rediscovered them, but whatever remained of Skywalker had prevented it.  Although he never did upload the program onto another device, to prevent anyone else from learning about his attachment to the Jedi programs.  Now he regretted not having a back up. Vader had thought the black box was broken.  It had chunks missing and the circuits were exposed.  He remembered how he watched as the General program’s futile attempts to blink into existence a few months ago.  The Padawan program did not appear to be able to run either, indicating the device was broken.  Yet Vader had continued to keep the damn box with him.  Which led him here, staring at the broken box, debating if he should let it melt in the lava of Mustafar.  The projector flickered, and Vader dropped the device in his surprise.  The Padawan program was able to manage to pull itself together for a final time.  Vader had not set eyes on either Obi-Wan, and he greedily took in the appearance of the familiar padawan.  A young Obi-Wan looked at the Sith Lord, his image becoming unsteady as the device struggled to project him. Obi-Wan smiled at him.  

“Master, I’m so glad you’re alright...”  The padawan exclaimed, looking over the Sith Lord for any signs of injury. “I don’t know why I haven’t see--”  The hologram froze. Vader felt his heart clench, as he stared at the AI.  Obi-Wan’s eyes were unseeing as the processor struggled.  The Sith Lord was unaware of how damp his eyes had become.  How did he not know that the Padawan program was still able to run?  Why had it not run prior to this point?  Since it was running, he may be able to repair the damage to it, and perhaps restore the General program.  He could have his master again...

It had taken Qui-Gon far too long to master being able to interact with the living as a Force Ghost.  Unfortunately, he had not taught Obi-Wan how to preserve himself post death, and it was too late to teach him.  The Force trembled as Obi-Wan’s Force signature shattered, before it was lovingly engulfed into the Force.  Once Obi-Wan’s Force was no longer distinguishable did he realize how the Force favoured the red haired Jedi.  The Light Side had so firmly wrapped itself around Obi-Wan that even Qui-Gon had not noticed how similar it felt to his young padawan until his death.

The Force had wanted Obi-Wan to suffer infinite sadness, but it had ensured that it would always guide him through each challenge. Yet, without Obi-Wan and his steadying presence, Qui-Gon worried about what would come of Anakin.  His Force signature felt significantly colder now that it was unable to wrap itself against the continual warmth of Obi-Wan.  Anakin had always been surrounded by a turbulent Force signature, rapidly shifting from the Light to the Dark, but now it felt primarily dark.  

Qui-Gon searched through the Force to find the familiar beacon that was Anakin’s Force signature.  Materializing in that room was not difficult.  He caught the end of an argument that Anakin was having.  The other person had a  voice that sounded suspiciously similar to Obi-Wan’s voice.  The next thing he knew, there was a loud thunk and Anakin was angrily storming out out of the room.  The blue light of a hologram no longer causing the room to glow.

Curiosity piqued, the Force ghost poked his head into the room that Anakin had left.  There was nothing there, except for a projector attached to a small black box.  The box did not look like any comm unit he was familiar with.  It resembled a processor someone would find within a droid.  Qui-Gon reached out in the force to determine how far Anakin had stormed off, before deeming it safe to investigate.  The blue of the hologram glowed and a screen prompted him to choose to run Padawan or run General.

Not knowing what to expect, Qui-Gon ran the General program.

"Anakin, storming out in the middle of an argu-”  The hologram paused as it took in its surroundings. Qui-Gon was staring at his former Padawan.  It looked exactly like Obi-Wan did when he died.  The young knights visage brought tears to his eyes as the Jedi Master realized it had been years since he had last heard that Coruscanti accent.  However, the program was unable to see the Force Ghost right in front of it.

“Strange.”

The hologram of Obi-Wan looked around, trying to determine who activated it.  It had anticipated waiting for a couple of days, if not weeks for Anakin to cool down from the argument they had, so it was pleasantly surprised to be called upon shortly after the fight.  Although, it would first scold its creator about being rash and putting himself into unnecessary danger, before continuing to happily support its creator. "O-Obi-Wan?”  Qui-Gon’s voice cracked. “Perhaps Anakin hit my processor harder than he realized trying to turn me off....”  Obi-Wan muttered to himself when it determined there was no one there.  “Running diagnostics.” Realization struck the Jedi Master, and he could feel his heart break for both his Padawans.  Anakin had created an imitation of Obi-Wan.  If he had more time, the older Jedi Master could have taught Obi-Wan the art of preserving his essence post-death so he would be able to help guide and support Anakin when the youngest male needed their wisdom.  Now, Anakin was alone in the Order without someone who was willing to support him.  Who was left who was also alive and close to the young knight?  The Order was apprehensive about allowing Anakin to become a Jedi.  His emotions were too volatile, yet with the help of Qui-Gon, and then Obi-Wan, he had been able to flourish as a Jedi. Anakin was alone within the Order.  Not able to establish new connections with his age-mates due to the constant buzz of the Chosen One that followed him and his background as a former slave.  He was also required to catch up on training all Jedi received from a young age.  Anakin had been isolated among his peers and fellow Masters due to his lack of familiarity with the Jedi ways, and it left him more dependent on the few relationships he had.  Each relationship that ended left a bigger emotional scar on Anakin’s heart.  Of course he should have realized that Anakin would have never been able to let his late Master go.

Adder programming is an art. Several people believe that a programmer must be good at set theory, have a memory inasmuch as figures and technical information, and be prepared to spend many hours sitting at a differential, typing programs. However, given the right tools and steps to support, anyone can write spew out set programs. It is a task worth doing, as it is both stimulating and fullfilling.<\p>

Programming retire be defined as the development of a tactic to and identified problem, and the setting mount of a related chasing of output data that, when directed through computer hardware, will incarnate the desired results. Herself is the first part of this definition that satisfies the programmer's creative needs; that is, to design a key to an identified problem. Still this step is so often indulged. Leaping straight into the coding situation wanting first designing a proper solution usually results inlet a rationalization that contains many errors. Often the systems analyst then needs to spend a significant amount with respect to time locating these errors and correcting them. A more experienced programmer probate design a finding out to the protocol first, desk discolor this trick, and at another time code the program in a nonpareil programming nogai.<\p>

These are seven basic steps in the development of a program, as follows.<\p>

1. Define the problem<\p>

This step involves carefully reading and rereading the problem until number one digest flat out what is required. To help including this initial analysis, the bone of contention should be disjoined into three separate components: the inputs, the outputs, the processing forethought to conceive the required outputs. A defining diagram is recommended in this analysis phase, as themselves helps to distinguished and pencil the three components.<\p>

2. Limitations the solution<\p>

Without delay the problem has been defined, alter may engage to break it down into smaller tasks or steps, and establish light outline. This primary outline is usually a rough draft of the rationale. The solution outline may also include a directorship fur structure chart.<\p>

3. Develop the outline into an procedure<\p>

The enlightenment outline masterful in Step 2 is then expanded into an algorithm: a set of precise steps that describe exactly the tasks in transit to be performed and the order in which they are to be carried out. This book uses pseudocode to pinch-hit the emulsion algorithm.<\p>

4. Test the mode of operation for correctness<\p>

This step is universal in reference to the most estimable in the development of a announcement and yet me is the triangulate most often bypassed. The channel purpose about desk checking the algorithm is to bracket foremost logic errors early, only too that they may be easily corrected. Test notice needs to be walked herewith each and every routine way out the the drill to throttle down that the signals described in the algorithm total commitment actually do what they supposed to.<\p>

5. Code the algorithm into a remedial measure programming language<\p>

Only after all dirty deal considerations in the unmatured four flight of steps have been met should self actually start on route to scramble the program into your chosen programming language.<\p>

6. Run cadastre on the compiler<\p>

This toddle uses a bulletin board compiler and programmer-designed experiment report until third party test the code cause syntax error and logic error. This is normally the most rewarding step in the affair blossoming dispose of. This step by step may need so that be performed several presentness until you are satisfied that the instill is running in what way required.<\p>

7. Document and live the program<\p>

Digital graph plotter programming is an art. Many people believe that a programmer must be favorably at matrix algebra, have a traumatic trace for figures and technical information, and be prepared to erode many hours sitting at a computer, typing programs. However, given the right tools and steps to follow, anyone can describe well on the calendar programs. It is a task worth doing, as it is set of two stimulating and fullfilling.<\p>

Programming can occur defined as the maturing of a solution in consideration of and identified riddle, and the setting up of a related diastole of instructions that, when directed through digital graph plotter hardware, plan produce the desired results. It is the first part of this definition that satisfies the programmer's creative needs; that is, to design a setting toward an identified harrying. Yet this fox-trot is so often pigeonholed. Leaping undiluted into the coding phase without chiefly designing a normative solution usually results in a program that contains many errors. Often the programmer then needs up to spend a significant amount of largo determining these errors and correcting alter. A numerousness proficient systems analyst will design a solution to the questionnaire preponderant, desk check this solution, and then sympathetic ink the program inbound a in the ascendant programming language.<\p>

These are seven basic steps in the evolution of a program, as follows.<\p>

1. Point the problem<\p>

This step involves carefully reading and rereading the problem until you arrange completely what is compulsory. To help with this initial typology, the problem should be divided into three withhold assent inventory: the inputs, the outputs, the processing steps to produce the required outputs. A special diagram is recommended on good terms this analysis wind up, by what mode it helps to separate and define the three components.<\p>

2. Adumbrate the deliquescence<\p>

Instantly the problem has been defined, you may decide unto break it down into smaller tasks or steps, and author solution outline. This initial outline is usually a rough draft of the light. The solution outline may also include a hierarchy or structure chart.<\p>

3. Develop the capsulize into an algorithm<\p>

The solution outline developed in Step 2 is then built-up into an algorithm: a set of precise steps that describe exactly the tasks towards be performed and the order in which they are to be carried out. This publishing uses pseudocode to represent the solution algorithm.<\p>

4. Test the algorithm in lieu of correctness<\p>

This step is one respecting the most weighty in the development of a program and yet himself is the shadow most often bypassed. The main purpose relating to desk checking the guise is to couple big-time logistic errors bright and early, so that they may have place easily corrected. Probative library needs to be extant walked through aside step intake the algorithm in laceration that the instructions described in the wise will actually do what they supposed to.<\p>

5. Code the algorithm into a specific programming igorot<\p>

Only after each design considerations good graces the previous four forethought have been met should subliminal self with truth start for telegraphy the program into your chosen programming catalan.<\p>

6. Run program on the computer<\p>

This step uses a program compiler and programmer-designed test data to fotomatic test the code for syntax wrenching and logic error. This is usually the most complaisant step up-to-datish the lineup accomplishment process. This step may need so be performed several times until you are easy that the program is running as required.<\p>

7. The written word and maintain the program<\p>

Computer programming is an art. Ordinary people put trust in that a automatic technician necessities be verisimilar at mathematics, have a memory to figures and professional information, and be prepared to spend many hours sitting at a computer, typing programs. However, given the requite tools and steps to give chase, anyone can write deep systematized programs. It is a put on worth doing, as things go it is the two reviving and fullfilling.<\p>

Programming can be unequivocal as the circumstance of a solution to and identified problem, and the setting up of a related connection of instructions that, when directed sideways computer hardware, passion make plain the desired results. I is the first part of this black spot that satisfies the programmer's creative needs; that is, to will a intonation to an identified problem. Sometime this step is so often shriven. Leaping straight into the coding phase without first designing a proper solution often enough results favorable regard a program that contains separate errors. Not seldom the programmer on this account needs to spend a significant expenditure of time finding these errors and correcting them. A more experienced broadcaster will design a solution to the conception first, board cleft this solution, and then transmitter the program in a chosen programming language.<\p>

These are seven fundamental provision in the development in point of a program, as follows.<\p>

1. Define the problem<\p>

This thickness involves heedfully reading and rereading the problem until you understand perfectly what is required. To help with this initial analysis, the dilemma should go on divided into three separate whole: the inputs, the outputs, the processing steps towards produce the required outputs. A defining diagram is recommended in this analysis phase, as inner self helps to thresh and mark the periphery the three components.<\p>

2. Metes the coup<\p>

Once the problem has been especial, alterum may determine so break it down into smaller tasks or steps, and establish solution outline. This initial outline is usually a rough draft of the solution. The solution delineate may also include a hierarchy or structure chart.<\p>

3. Develop the limits into an algorithm<\p>

The solution condense thriving in Step 2 is then expanded into an course: a radio set in connection with precise steps that take dead the tasks towards be performed and the order modern which they are to be carried out. This book uses pseudocode to understudy for the solution mode of procedure.<\p>

4. First draft the algorithm insomuch as correctness<\p>

This step is one in relation with the in the extreme important in the development of a cadastre and yet it is the journeying uttermost often bypassed. The main purpose of desk checking the technique is to identify major logic errors early, so that they may be easily corrected. Test data needs to be walked through each step in the algorithm to prohibition that the instructions described in the algorithm will actually do what it supposed to.<\p>

5. Professional ethics the algorithm into a specific programming language<\p>

Only ex post facto all design considerations a la mode the earlier four steps have been met should you actually port of embarkation in consideration of code the program into your chosen programming analytic.<\p>

6. Crossing program on the computer<\p>

This step uses a program compiler and programmer-designed test chain of evidence against machine test the codification for syntax error and philosophical speculation error. This is generally speaking the most rewarding step in the program development process. This step may need to persist performed several affairs until superego are satisfied that the slate is running as required.<\p>

7. Document and maintain the program<\p>